Uptime.com incident

Decommissioning of Probe Server IP Addresses - 8 July 2026

Minor Ongoing

Uptime.com is currently experiencing a minor incident, which began 3d ago. The vendor's full update timeline is below.

Started
Jul 02, 2026, 12:00 AM UTC
Resolved
Ongoing
Duration
● 3d 2h
Detected by Pingoru
Jul 02, 2026, 12:00 AM UTC

Update timeline

  1. monitoring Jul 02, 2026, 12:00 AM UTC

    As part of our ongoing infrastructure improvements, we are replacing probe servers across several regions. As a result, the following IP addresses will be retired and removed from the Uptime.com IP monitoring range list: **Australia-Sydney:** - `172.105.184.135` - `45.77.233.193` - `2400:8907::f03c:92ff:fef4:b360` - `2401:c080:1800:409e:5400:04ff:fedb:eada` **Bulgaria-Sofia:** - `37.252.247.38` - `2a00:11c0:2b:777::4` **South Africa-Johannesburg:** - `139.84.238.199` - `139.84.237.51` - `2a05:f480:3000:2b9d:5400:04ff:fedf:d612` - `2a05:f480:3000:28af:5400:04ff:fedb:eac3` **Japan-Tokyo:** - `167.179.70.103` - `172.104.78.192` - `45.76.202.148` - `2001:19f0:7001:ecc:5400:04ff:fe5e:b3cc` - `2400:8902::f03c:91ff:fef2:13b9` - `2001:19f0:7002:0804:5400:04ff:feff:c581` ### **Action Required:** If you have configured firewall ACLs or allowlists that include any of the IP addresses above, please remove or update those rules starting **8 July 2026** to prevent unintended access policy conflicts. No action is required if you do not explicitly allowlist Uptime.com probe server IPs in your infrastructure. If you have any questions or need assistance, please don't hesitate to contact our support team.