Shared Infrastructure

All times in local timezone

All systems operational

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

(Viewing historical data)

Uptime (Jan 2025 - Jun 2025)

99.93%

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.

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

API Unavailable

Incident Resolved 16m
Major outage
Resolved

We have identified the root cause and have reverted the changes made that affected our API. The root cause was linked to a routine server dependency update, that was reverted to resolve the incident

Identified

We are currently experiencing an incident affecting our API, causing it to be unavailable. Our team is investigating the issue and working to restore service as quickly as possible. We will provide further updates shortly.

API Unavailable

Incident Resolved 13m
Major outage
Resolved

The issue affecting our API has been resolved, and services are now operational. We are continuing to monitor the situation closely to ensure stability.

Identified

We are currently experiencing an incident affecting our API, causing it to be unavailable. Our team is investigating the issue and working to restore service as quickly as possible. We will provide further updates shortly.

Performance Degradation Incident

Incident Resolved 2h 17m
Major outage
Resolved

The performance issues (including slowness and potential access problems) reported earlier this morning, following our recent system maintenance, have now been fully resolved. Our team has completed the necessary corrective actions, and all services have returned to normal operation. We have confirmed that system performance is stable. We apologize for the disruption this may have caused and thank you for your patience and understanding while we worked to resolve it.

Identified

Our monitoring systems have detected performance issues impacting services following overnight maintenance completed early on April 23rd. Users may experience slowness or difficulty accessing the platform. Our engineers are investigating urgently. We apologize for the inconvenience and will share more information shortly.

Instabilities with search feature

Incident Resolved 3h 2m
Degraded performance
Resolved

Search feature is now fully functional

Identified

Search feature is unstable