Shared Infrastructure

All times in local timezone

All systems operational

We're not aware of any issues affecting our systems.

(Viewing historical data)

Uptime (Jul 2024 - Dec 2024)

99.99%

How uptime is calculated

Uptime = (Total time - Contractual downtime) / Total time

"Contractual downtime" is the period during which Fabriq is unavailable as commonly defined in our commercial contracts. It includes any periods of partial or full outages, excluding when Fabriq's liability is waived (e.g. unavailability due to natural disasters or third parties outside Fabriq's control). It does not include periods of degraded performance or scheduled maintenance.

2024-07-01: operational 2024-07-02: operational 2024-07-03: operational 2024-07-04: operational 2024-07-05: operational 2024-07-06: operational 2024-07-07: operational 2024-07-08: operational 2024-07-09: operational 2024-07-10: operational 2024-07-11: operational 2024-07-12: operational 2024-07-13: operational 2024-07-14: operational 2024-07-15: operational 2024-07-16: operational 2024-07-17: operational 2024-07-18: operational 2024-07-19: operational 2024-07-20: operational 2024-07-21: operational 2024-07-22: operational 2024-07-23: operational 2024-07-24: operational 2024-07-25: operational 2024-07-26: operational 2024-07-27: operational 2024-07-28: operational 2024-07-29: full_outage 2024-07-30: operational 2024-07-31: operational 2024-08-01: operational 2024-08-02: operational 2024-08-03: operational 2024-08-04: operational 2024-08-05: operational 2024-08-06: operational 2024-08-07: operational 2024-08-08: operational 2024-08-09: operational 2024-08-10: operational 2024-08-11: operational 2024-08-12: operational 2024-08-13: operational 2024-08-14: operational 2024-08-15: operational 2024-08-16: operational 2024-08-17: operational 2024-08-18: operational 2024-08-19: operational 2024-08-20: operational 2024-08-21: degraded_performance 2024-08-22: degraded_performance 2024-08-23: operational 2024-08-24: operational 2024-08-25: operational 2024-08-26: operational 2024-08-27: operational 2024-08-28: operational 2024-08-29: operational 2024-08-30: operational 2024-08-31: operational 2024-09-01: operational 2024-09-02: operational 2024-09-03: operational 2024-09-04: operational 2024-09-05: operational 2024-09-06: operational 2024-09-07: operational 2024-09-08: operational 2024-09-09: operational 2024-09-10: operational 2024-09-11: full_outage 2024-09-12: operational 2024-09-13: operational 2024-09-14: operational 2024-09-15: operational 2024-09-16: degraded_performance 2024-09-17: operational 2024-09-18: operational 2024-09-19: operational 2024-09-20: operational 2024-09-21: operational 2024-09-22: operational 2024-09-23: operational 2024-09-24: operational 2024-09-25: operational 2024-09-26: operational 2024-09-27: operational 2024-09-28: operational 2024-09-29: operational 2024-09-30: operational 2024-10-01: operational 2024-10-02: operational 2024-10-03: operational 2024-10-04: operational 2024-10-05: operational 2024-10-06: operational 2024-10-07: operational 2024-10-08: operational 2024-10-09: operational 2024-10-10: operational 2024-10-11: operational 2024-10-12: operational 2024-10-13: operational 2024-10-14: operational 2024-10-15: operational 2024-10-16: operational 2024-10-17: operational 2024-10-18: operational 2024-10-19: operational 2024-10-20: operational 2024-10-21: operational 2024-10-22: operational 2024-10-23: operational 2024-10-24: operational 2024-10-25: operational 2024-10-26: operational 2024-10-27: operational 2024-10-28: operational 2024-10-29: operational 2024-10-30: operational 2024-10-31: operational 2024-11-01: operational 2024-11-02: operational 2024-11-03: operational 2024-11-04: operational 2024-11-05: operational 2024-11-06: operational 2024-11-07: operational 2024-11-08: operational 2024-11-09: operational 2024-11-10: operational 2024-11-11: operational 2024-11-12: operational 2024-11-13: degraded_performance 2024-11-14: operational 2024-11-15: operational 2024-11-16: operational 2024-11-17: operational 2024-11-18: operational 2024-11-19: operational 2024-11-20: operational 2024-11-21: operational 2024-11-22: operational 2024-11-23: operational 2024-11-24: operational 2024-11-25: operational 2024-11-26: degraded_performance 2024-11-27: operational 2024-11-28: operational 2024-11-29: operational 2024-11-30: operational 2024-12-01: operational 2024-12-02: operational 2024-12-03: operational 2024-12-04: operational 2024-12-05: operational 2024-12-06: operational 2024-12-07: operational 2024-12-08: operational 2024-12-09: operational 2024-12-10: operational 2024-12-11: operational 2024-12-12: operational 2024-12-13: operational 2024-12-14: operational 2024-12-15: operational 2024-12-16: operational 2024-12-17: operational 2024-12-18: operational 2024-12-19: operational 2024-12-20: operational 2024-12-21: operational 2024-12-22: operational 2024-12-23: operational 2024-12-24: operational 2024-12-25: operational 2024-12-26: operational 2024-12-27: operational 2024-12-28: operational 2024-12-29: operational 2024-12-30: operational 2024-12-31: operational
Jul 2024 Dec 2024
Incident & Maintenance History (Jul 2024 - Dec 2024)

Async Tasks are taking a long time to run

Incident Resolved 4h 32m
Degraded performance
Resolved

All tasks enqueued during the last few hours have been concluded. All new tasks are being executed normally. We are taking steps to prevent administrative tasks to cause such interference again.

Identified

The system is normalizing itself and Tasks triggered in the last few hours are currently running.

Identified

We are aware that Asynchronous Tasks (which include, for example, Datapoint Imports) are taking a long time to run. This is due to the increased load in our Asynchronous Tasks system caused by internal administrative tasks.

API is degraded

Incident Resolved 10m
Degraded performance
Resolved

API is back to normal. Resolved itself after those requests have been treated.

Identified

Our system experiences some slowness due to a high number of requests.

Unavailability on specific regions (Application, API)

Incident Resolved 1h 32m
Degraded performance
Resolved

We confirm that the all issues are over. The app is now reliably available on Asia, North America, and Australia. Live updates (on all regions) are also working properly.

Identified

Our networking provider, Cloudflare, reported that they are experiencing difficulties at the moment. Those difficulties match up with the issues we are experiencing. No action can be performed on our part to alleviate those issues. A detailed report can be found here: https://www.thousandeyes.com/blog/cloudflare-outage-analysis-september-16-2024

Identified

We are aware that our live updates system is also unavailable across all regions. This affects the web and mobile applications, which will fail to live update when other users perform changes.

Identified

We confirm that the outage is localized to those regions and does not affect Europe.

Identified

We are aware that the application is unavailable on Europe, Asia, and North America regions. This affects the API and our Web and Mobile application on those regions. We are investigating.

Downtime on API

Incident Resolved 2m
Major outage
Resolved

The usage of the database is back to normal. We are still monitoring and investigating about what caused this incident.

Identified

We're experiencing an issue that put the API down. We identified a peak of usage of our database. We are making actions to resolve the issue and investigate.

Routine usage within a time period resulted in invalid data

Incident Resolved 19h 20m
Degraded performance
Resolved

The bug regarding Routines has been fixed, but unfortunately the correct data from that period cannot be recovered. We will assist the recovery of our customers' operations in the following way: - Providing a list of the affected Routine Executions that have invalid data. - Offering to remove the affected Routine Executions. - Rebuilding the data on Dynamic KPIs that are based on those Routines.

Identified

Due to a regression introduced by a change in the application, from Wednesday 2024-08-21 01:04 PM UTC to Thursday 2024-08-22 8:24 AM UTC, any usage of Routines resulted in invalid data being recorded. This was due to a bug that displayed incorrect Routine Steps when starting, submitting, or editing a Routine Execution; and when editing the Steps of Routines. When used during that time period, Routines were missing some Steps, or had Steps that were displayed or recorded data in an unexpected way. Therefore, the data on those Routine Executions is invalid and cannot be exploited. Dynamic KPIs based on those Routine Executions will also display incorrect data. The issue affected the Webapp, the Mobile Application, and the ability to retrieve data from Routines on our public API.

API is down

Incident Resolved 11m
Major outage
All systems operational
Resolved

The root cause comes from a feature that was supposed to improve the loading time of images and avatars. This feature was intended to enhance the way thumbnails are managed in the legacy code. This improvement has been postponed and will be implemented in the new stack.

Monitoring

Service on the API is restored. We are investigating the cause of the incident.

Identified

We're experiencing an issue that put the API down. We are making actions to resolve the issue and investigate.