All Systems Operational
API Operational
90 days ago
100.0 % uptime
Today
Web Application Operational
90 days ago
99.98 % uptime
Today
Public Dashboards Operational
90 days ago
100.0 % uptime
Today
Check Scheduler Operational
90 days ago
100.0 % uptime
Today
Browser check runtime Operational
90 days ago
99.96 % uptime
Today
Deployments Operational
90 days ago
100.0 % uptime
Today
Alerting Operational
90 days ago
100.0 % uptime
Today
Private Location Operational
90 days ago
100.0 % uptime
Today
API Check Runtime Operational
90 days ago
99.96 % uptime
Today
Multistep check runtime Operational
90 days ago
99.96 % uptime
Today
Test session Operational
90 days ago
100.0 % uptime
Today
Heartbeat check Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Past Incidents
Feb 20, 2025

No incidents reported today.

Feb 19, 2025
Resolved - This incident has been resolved.
Feb 19, 19:46 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 19, 19:25 UTC
Identified - The issue has been identified and a fix is being implemented.
Feb 19, 19:23 UTC
Investigating - We are experiencing a scheduling delay in the region us-west-2 and are currently investigating the root issue.
Feb 19, 18:54 UTC
Resolved - This incident has been resolved.
Feb 19, 14:22 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 19, 14:12 UTC
Investigating - We are investigating an increase in the error rate related to one of our storage providers.
Feb 19, 13:29 UTC
Feb 18, 2025

No incidents reported.

Feb 17, 2025

No incidents reported.

Feb 16, 2025

No incidents reported.

Feb 15, 2025

No incidents reported.

Feb 14, 2025
Resolved - This incident has been resolved.
Feb 14, 01:43 UTC
Monitoring - The region has recovered for now and is operating normal. We are continuing to monitor the situation.
Feb 14, 00:47 UTC
Update - We see the region recovering and check runs picking up. It is currently processing a large backlog of checks, so scheduling delay might still be high for a few more minutes.
Feb 14, 00:34 UTC
Identified - The region is still affected and we are tracking the incident at AWS. Currently we are looking into a way to mitigate the impact for Checkly customers.
Feb 14, 00:05 UTC
Investigating - We have identified an incident in scheduling checks in eu-north-1 (Stockholm). The issue is caused by an incident impacting our hosting provider, AWS. As a result, checks running in eu-north-1 (Stockholm) will not run on their configured schedule.
Feb 13, 23:43 UTC
Feb 13, 2025
Feb 12, 2025

No incidents reported.

Feb 11, 2025

No incidents reported.

Feb 10, 2025

No incidents reported.

Feb 9, 2025

No incidents reported.

Feb 8, 2025

No incidents reported.

Feb 7, 2025

No incidents reported.

Feb 6, 2025
Resolved - The Cloudflare incident has been resolved.
Feb 6, 10:31 UTC
Update - We are continuing to monitor for any further issues.
Feb 6, 09:23 UTC
Monitoring - We do not see any failures for this incident since 09:13 UTC across our infra. We keep monitoring the situation.
Feb 6, 09:18 UTC
Update - The upstream incident is ongoing. The following workarounds exist for affected and failing checks:

1. disable the check.
2. remove the `.toHaveScreenshot()` assertion from checks and rerun the check once with `Run script and update golden files` then save. Be careful, it might be the only useful assertion of your check.

We keep monitoring the situation closely and keep sending updates here.

Feb 6, 09:13 UTC
Update - The upstream incident is here https://www.cloudflarestatus.com/incidents/pgz7g5xlpxzr
Feb 6, 08:39 UTC
Identified - Currently only checks using the visual regression & snapshot testing are affected. We see an incident at an upstream provider (Cloudflare).
Feb 6, 08:35 UTC
Investigating - We see an elevated increase of check runs across some regions failing with `Unable to run the check, please contact support`. We are investigating
Feb 6, 08:21 UTC