Uptime.com incident
Incorrect v4 IPs used in Austria-Vienna, Germany, Bulgaria-Sofia, Switzerland
Resolved after 6 minutes, on September 30, 2026.
From Sep 29, 2:00 PM to Sep 30, 1:30 PM, 5 probe locations did not use the IPv4 addresses that are on our published probe list. During this time, these locations sent checks from their native provisioned IPv4 addresses. Checks continued to run from the correct locations and the results were correct. But if your firewall or allowlist permits only the IPv4 addresses on our probe list, checks from these locations were possibly blocked. This can cause false alerts. We found and fixed the cause. All traffic from these locations now goes through the IPv4 addresses on our published probe list again. You do not need to do anything.
Update timeline
- resolved Sep 30, 2026, 01:38 PM UTC
From Sep 29, 2:00 PM to Sep 30, 1:30 PM, 5 probe locations did not use the IPv4 addresses that are on our published probe list. During this time, these locations sent checks from their native provisioned IPv4 addresses. Checks continued to run from the correct locations and the results were correct. But if your firewall or allowlist permits only the IPv4 addresses on our probe list, checks from these locations were possibly blocked. This can cause false alerts. We found and fixed the cause. All traffic from these locations now goes through the IPv4 addresses on our published probe list again. You do not need to do anything.
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