The issue has been resolved.
May 19 07:45:18 (UTC)From 14:49-14:55UTC there was a delay in processing some check runs. This incident is now resolved, and all checks are again being processed at their scheduled frequency.
May 14 14:49:00 (UTC)Check runs on eu-west-2 London experienced an interruption from 7:57UTC to 8:20UTC. This resulted in an increased scheduling delay and also an increase in check failures due to timeouts. This issue is now resolved and check runs in eu-west-2 London are running normally.
May 12 07:57:00 (UTC)The issue has been resolved.
May 5 10:47:50 (UTC)Between 07:26 and 9:00 UTC, check sessions were incorrectly marked as cancelled, and alerts that depend on status changes were not sent. A deployment error caused check sessions to be recorded as cancelled instead of their actual status (passed, degraded, or failed). Your home dashboard and check result pages may show cancelled sessions and outdated check statuses from this timeframe. We are actively working to correct the affected session data so your dashboard and check statuses reflect accurate results.
Apr 30 10:52:59 (UTC)The issue has been resolved.
Apr 22 19:14:08 (UTC)We are currently unable to run checks from our Bahrain region due to circumstances outside of our control. If you have monitors configured to run from Bahrain, those checks are not executing at this time. We recommend switching to an alternative region in your check settings to maintain coverage in the meantime.
Mar 24 09:59:42 (UTC)Cloudflare's scheduled maintenance is complete, the network degradation in us-east-1 has recovered.
Mar 6 13:12:34 (UTC)Due to a major AWS infrastructure outage in me-south-1, we will not be scheduling checks in this region until the situation is resolved. https://health.aws.amazon.com/health/status
Mar 2 06:38:08 (UTC)