Cerby Outage History

Cerby is up right now

Cerby had 2 outages in the last 2 years totaling 6h 51m of downtime — averaging 0.1 incidents per month.

There were 2 Cerby outages since March 11, 2026 totaling 6h 51m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cerby.com

Notice July 1, 2026

Cerby Service Interruption

Detected by Pingoru
Jul 01, 2026, 12:00 AM UTC
Resolved
Jul 01, 2026, 12:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Jul 01, 2026, 10:00 PM UTC

    — This incident has been resolved. Service was fully restored at 7:08 PM CST. We identified a spike in database load caused by a combination of API traffic and scheduled integration jobs, and resolved it by applying rate limits to the affected traffic. All delayed automation jobs have since completed successfully. Jun 30, 2026 · 19:20 CST Monitoring — A mitigation has been applied, and service has been restored. We are continuing to monitor to confirm full stability. Jun 30, 2026 · 19:10 CST Identified — We have identified the source of increased database load and are applying a fix. Jun 30, 2026 · 18:45 CST Investigating — We are investigating reports of degraded performance affecting the Cerby Web App, API, and Automation services. Jun 30, 2026 · 18:15 CST Affected components: Web App, API, Automation

Read the full incident report →

Minor March 11, 2026

Cerby-managed non-VoIP phone number provisioning and SMS Delays

Detected by Pingoru
Mar 11, 2026, 06:23 PM UTC
Resolved
Mar 12, 2026, 01:15 AM UTC
Duration
6h 51m
Affected: Cerby Web App
Timeline · 3 updates
  1. investigating Mar 11, 2026, 06:23 PM UTC

    We are currently experiencing issues provisioning new non-VoIP Cerby-managed phone numbers and receiving SMS on existing non-VoIP numbers. Our team is actively investigating to identify the root cause.

  2. investigating Mar 12, 2026, 01:14 AM UTC

    We are continuing to investigate this issue.

  3. resolved Mar 12, 2026, 09:36 AM UTC

    This incident has been resolved.

Read the full incident report →