Calibre Outage History

Calibre is up right now

Pingoru has recorded 32 incidents for Calibre: 3 in the last 12 months and 0 in the last 90 days.

Source: calibrestatus.com

32incidents recorded
3last 12 months
0last 90 days
12 daystypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Calibre in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20261336 of 720 (47%)
May 202612 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 507 (0%)

Incidents, newest first

Minor May 6, 2026 Application performance 1h 54m Application

Started May 06, 2026, 10:32 AM UTC· resolved May 06, 2026, 12:27 PM UTC

  1. identified May 06, 2026, 10:32 AM UTC

    We have identified degraded performance from the application and are monitoring it.

  2. resolved May 06, 2026, 12:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 1, 2026 Synthetic testing unavailable in Bahrain 35d 12h Bahrain

Started Apr 01, 2026, 11:42 PM UTC· resolved May 07, 2026, 12:24 PM UTC

  1. identified Apr 01, 2026, 11:42 PM UTC

    Our synthetic page speed monitoring service is currently unavailable in Bahrain due to the illegal war in the region. Our services in the region are offline and unable to be contacted at this time. It may be some time before they become available again. More updates as they come.

  2. resolved May 07, 2026, 12:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 21, 2026 Degraded application performance 42m Application, CLI & Node.JS API

Started Jan 21, 2026, 12:00 AM UTC· resolved Jan 21, 2026, 12:43 AM UTC

  1. investigating Jan 21, 2026, 12:00 AM UTC

    We are currently investigating a degradation in application performance.

  2. monitoring Jan 21, 2026, 12:12 AM UTC

    Application performance has returned to acceptable levels. We are monitoring before resolving.

  3. resolved Jan 21, 2026, 12:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 20, 2025 Test delays 15h 7m Sydney, São Paulo, Canada, Frankfurt and 13 more

Started Oct 20, 2025, 11:00 AM UTC· resolved Oct 21, 2025, 02:07 AM UTC

  1. identified Oct 20, 2025, 11:00 AM UTC

    Due to AWS incident with various services, we are experiencing delays in tests for North Virginia, California & Oregon. North Virginia is currently the most impacted.

  2. identified Oct 20, 2025, 11:07 AM UTC

    Tests are running in all other locations, however their processing is delayed so results will be stalled until AWS recovers.

  3. monitoring Oct 20, 2025, 11:21 AM UTC

    The test results backlog is processing. Tests in North Virginia are not running, we are monitoring.

  4. monitoring Oct 20, 2025, 07:48 PM UTC

    Testing in North Virginia continues to be interrupted by AWS outage. All other regions are operational.

  5. monitoring Oct 20, 2025, 08:22 PM UTC

    North Virginia is back, the test backlog is being processed. We are monitoring.

  6. resolved Oct 21, 2025, 02:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 29, 2025 Application unavailable 13m Application

Started May 29, 2025, 02:05 AM UTC· resolved May 29, 2025, 02:18 AM UTC

  1. investigating May 29, 2025, 02:05 AM UTC

    We are currently investigating this issue.

  2. identified May 29, 2025, 02:11 AM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved May 29, 2025, 02:18 AM UTC

    This incident has been resolved.

Read the full incident report →