Uptime.com incident
Check Configuration Propagation Delays Across Multiple Locations
Update timeline
- investigating Apr 02, 2026, 04:20 PM UTC
We are currently investigating an issue affecting the propagation of check configurations across multiple probe servers and locations. Newly created checks, as well as updates to existing checks, may not be reaching probe servers as expected. As a result, new checks may not start running and configuration changes may be delayed. Our engineering team is actively investigating the issue. We will provide further updates as soon as more information becomes available.
- monitoring Apr 02, 2026, 05:38 PM UTC
We have identified the issue affecting check configuration propagation across multiple probe servers and locations. The problem was introduced by a recently deployed development change, which has now been reverted. We are currently running the reconfiguration process to ensure newly created checks and configuration updates are applied correctly across affected probe servers. We are actively monitoring recovery and verifying that checks are being reconfigured as expected. Further updates will be provided if needed.
- resolved Apr 02, 2026, 06:33 PM UTC
The issue affecting check configuration propagation across multiple probe servers and locations has been resolved. A full reconfiguration has been completed and all checks and configuration updates are now being applied as expected. We will continue to monitor to ensure stability.
Looking to track Uptime.com downtime and outages?
Pingoru polls Uptime.com's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Uptime.com reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Uptime.com alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required