Lonza

All times in local timezone

All systems operational

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

(Viewing historical data)

Uptime (Jan 2026 - Jun 2026)

99.98%

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.

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

Increased usage is causing degraded performance

Incident Resolved 1m
All systems operational
Degraded performance
Resolved

System is back to normal performance.

Monitoring

Usage of labels feature has decreased at its normal performance.

Investigating

Increased usage of the labels feature is causing an increased usage of resources, which is causing degraded performance.

Degraded performance

Incident Resolved 1h 7m
Degraded performance
Resolved

The issue is due to latency on AWS's side : https://health.aws.amazon.com/health/status?eventID=arn:aws:health:eu-west-3::event/EC2/AWS_EC2_OPERATIONAL_ISSUE/AWS_EC2_OPERATIONAL_ISSUE_FB70E_B77B1D343FD

Investigating

Degraded performance from the backend

Latency issue detected

Incident Resolved 15m
Degraded performance
Resolved

The incident is now resolved.

Monitoring

The fix has been applied, everything should work normally now.

Identified

The problem is identified, we're are currently deploying a fix that should be available in 5min

Investigating

We identify that there is some latency with all Fabriq environments

Investigating

We identify that there is some latency with all Fabriq environments

Degraded performance

Incident Resolved 1h 25m
Degraded performance
Partial outage
Resolved

The app should be fully available now.

Investigating

We are experiencing degraded performance on the app. Investigation is on going.

The fabriq web application is down

Incident Resolved 10m
Partial outage
Resolved

A fix has been deployed. The web application is now working correctly.

Investigating

A blank page is displayed when accessing the web application. API is working correctly.