Calibre Outage History

Calibre is up right now

Calibre had 5 outages in the last 2 years totaling 870h 39m of downtime — averaging 0.2 incidents per month.

There were 5 Calibre outages since May 29, 2025 totaling 870h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.calibrestatus.com

Minor May 6, 2026

Application performance

Detected by Pingoru
May 06, 2026, 10:32 AM UTC
Resolved
May 06, 2026, 12:27 PM UTC
Duration
1h 54m
Affected: Application
Timeline · 2 updates
  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

Detected by Pingoru
Apr 01, 2026, 11:42 PM UTC
Resolved
May 07, 2026, 12:24 PM UTC
Duration
35d 12h
Affected: Bahrain
Timeline · 2 updates
  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

Detected by Pingoru
Jan 21, 2026, 12:00 AM UTC
Resolved
Jan 21, 2026, 12:43 AM UTC
Duration
42m
Affected: ApplicationCLI & Node.JS API
Timeline · 3 updates
  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

Detected by Pingoru
Oct 20, 2025, 11:00 AM UTC
Resolved
Oct 21, 2025, 02:07 AM UTC
Duration
15h 7m
Affected: SydneySão PauloCanadaFrankfurtLondonIrelandMumbaiTokyoSeoulSingaporeNorth VirginiaOhioNorthern CaliforniaOregonBahrainStockholmCape Town
Timeline · 6 updates
  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

Detected by Pingoru
May 29, 2025, 02:05 AM UTC
Resolved
May 29, 2025, 02:18 AM UTC
Duration
13m
Affected: Application
Timeline · 3 updates
  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 →