Uptime.com incident
Some checks incorrectly shown as down after brief failures
Ongoing since 11:35 AM UTC.
Between 11:35 and 13:10 UTC today, a change to our alerting caused some checks to be marked down after a single brief failure, even when the failure did not meet the check’s retry or location sensitivity settings. Affected checks may have sent down notifications and may still be showing as down, even though the service has since been reachable from our monitoring locations. We rolled back the change at 13:10 UTC, so new results are being handled normally again. We are now clearing the checks that are still incorrectly showing as down. No action is needed on your side.
Update timeline
- identified Oct 27, 2026, 11:35 AM UTC
Between 11:35 and 13:10 UTC today, a change to our alerting caused some checks to be marked down after a single brief failure, even when the failure did not meet the check’s retry or location sensitivity settings. Affected checks may have sent down notifications and may still be showing as down, even though the service has since been reachable from our monitoring locations. We rolled back the change at 13:10 UTC, so new results are being handled normally again. We are now clearing the checks that are still incorrectly showing as down. No action is needed on your side.
Your product runs on more than Uptime.com
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services