Uptime.com incident
Ping checks incorrectly reported as down on 23 monitoring locations
Resolved after 12 minutes, on November 4, 2026.
Between 13:05 and 13:17 UTC on November 4, 2026, Ping (ICMP) checks from 23 of our monitoring locations were incorrectly reported as down. During this period, affected Ping checks may have sent down notifications and recorded downtime even though the monitored hosts were reachable. Other check types were not affected. The issue was caused by a software update to our Ping monitoring service. During the rollout, the update was briefly applied with an incompatible configuration, which prevented Ping checks from running correctly at these locations. This issue was not caused by customer systems or configurations. The rollout completed at 13:17 UTC, and our engineering team has confirmed that Ping checks from all locations have been running normally since. No action is required from customers. Affected locations: - `Argentina-Buenos Aires` - `Australia-Melbourne` - `Austria-Vienna` - `Brazil-Sao Paulo` - `Canada-Toronto` - `Colombia-Bogota` - `Denmark-Copenhagen` - `Finland-Helsinki` - `France-Paris` - `Germany-Berlin` - `Germany-Frankfurt` - `Ireland-Dublin` - `New Zealand-Auckland` - `Philippines-Manila` - `Saudi Arabia-Riyadh` - `Switzerland-Zurich` - `United Arab Emirates-Dubai` - `US-CO-Denver` - `US-NV-Las Vegas` - `US-NY-New York` - `US-TX-Dallas` - `US-VA-Ashburn` - `US-WA-Seattle` We apologize for the incorrect alerts and are reviewing our release process to prevent this from happening again. If you have any questions, please feel free to contact our support team.
Update timeline
- resolved Nov 04, 2026, 01:05 PM UTC
Between 13:05 and 13:17 UTC on November 4, 2026, Ping (ICMP) checks from 23 of our monitoring locations were incorrectly reported as down. During this period, affected Ping checks may have sent down notifications and recorded downtime even though the monitored hosts were reachable. Other check types were not affected. The issue was caused by a software update to our Ping monitoring service. During the rollout, the update was briefly applied with an incompatible configuration, which prevented Ping checks from running correctly at these locations. This issue was not caused by customer systems or configurations. The rollout completed at 13:17 UTC, and our engineering team has confirmed that Ping checks from all locations have been running normally since. No action is required from customers. Affected locations: - `Argentina-Buenos Aires` - `Australia-Melbourne` - `Austria-Vienna` - `Brazil-Sao Paulo` - `Canada-Toronto` - `Colombia-Bogota` - `Denmark-Copenhagen` - `Finland-Helsinki` - `France-Paris` - `Germany-Berlin` - `Germany-Frankfurt` - `Ireland-Dublin` - `New Zealand-Auckland` - `Philippines-Manila` - `Saudi Arabia-Riyadh` - `Switzerland-Zurich` - `United Arab Emirates-Dubai` - `US-CO-Denver` - `US-NV-Las Vegas` - `US-NY-New York` - `US-TX-Dallas` - `US-VA-Ashburn` - `US-WA-Seattle` We apologize for the incorrect alerts and are reviewing our release process to prevent this from happening again. If you have any questions, please feel free to contact our support team.
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