Checkly Outage History

22 incidents recorded over the last 365 days, 18 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Checkly status99.25% uptime history

Every Recorded Checkly Incident

Checkly incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 10, 2026Security Notice: Unauthorized Access via Third-Party Analytics Tool0 minResolved
Jul 31, 2026Scheduling Disruption1 minResolved
Jul 18, 2026eu-central-1 (Checkly hosted) maintenancePlanned maintenance on Checkly infrastructure (eu-central-1). No service interruption expected.4h 0mScheduled
Jul 18, 2026us-west-1 (Checkly hosted) maintenancePlanned maintenance on Checkly infrastructure (us-west-1). No service interruption expected.4h 0mScheduled
Jul 17, 2026Elevated error rate 2h 16mResolved
Jul 16, 2026API Outage16 minResolved
Jul 2, 2026us-west-1 check scheduling issues3h 14mResolved
Jun 29, 2026Home dashboard not loading fully23 minResolved
Jun 29, 2026Partial homepage outage & check scheduling delays2h 16mResolved
Jun 25, 2026API 500 errors when updating or creating resources49 minResolved
Jun 18, 2026Increased Playwright check dependency installation failures in us-west-1 N. California1h 13mResolved
Jun 13, 2026us-east-1 (Checkly hosted) maintenancePlanned maintenance on Checkly infrastructure (us-east-1). No service interruption expected.8h 0mScheduled
Jun 13, 2026eu-west-2 (Checkly hosted) maintenancePlanned maintenance on Checkly infrastructure (eu-west-2). No service interruption expected.4h 0mScheduled
Jun 9, 2026Increased check failure rate and scheduling delay1h 14mResolved
May 28, 2026SMS Alerts Unavailable1h 54mResolved
May 19, 2026Increased scheduling delay affecting API checks and uptime monitors (us-west-1)45 minResolved
May 14, 2026Check scheduling delay0 minResolved
May 12, 2026eu-west-2 London - Check Run Interruption0 minResolved
May 5, 2026eu-west-2 running checks delayed10 minResolved
Apr 30, 2026Alerting Degraded52 minResolved
Apr 22, 2026Authentication broken24 minResolved
Mar 24, 2026me-south-1 not running checks4 minResolved

How to Read This Checkly Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Checkly acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Checkly outage in this window ran 8h, against a mean recovery of 1h 38m. If you depend on Checkly in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.