Albea

All times in local timezone

All systems operational

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

(Viewing historical data)

Uptime (Jan 2024 - Jun 2024)

100.00%

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

Regular short time Api outages (~5minutes) between 4:49 UTC and 9:05 UTC

Incident Resolved 4h 25m
Degraded performance
Resolved

At 9:14 UTC a fix was deployed and the incident is resolved Incident details: During the cleanup work done on KPIv3, a code error was introduced on an endpoint that serves calls coming from KPIv2. This caused calls coming from KPIv2 to freeze the server of the application. We investigated and found that the mobile app was still doing these calls, which was causing this issue. To correct this we did the following: - Stop calling KPIv2 from mobile and call KPIv3 directly - Repaire the error introduced during cleanup

Identified

The root cause was discovered, and the team started working on a fix

Investigating

Api outages

API not available

Incident Resolved 6m
Degraded performance
Resolved

Unexpected outage made the API not respond during 6 minutes. Services are now back to normal.