Uptime.com incident
Singapore, Australia-Sydney - Monitoring IP Mismatch
Uptime.com experienced a minor incident on October 1, 2026, lasting 14h 21m. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Oct 01, 2026, 01:00 AM UTC
#### Summary Some checks from the Singapore and Australia-Sydney locations used IP addresses that are not on our published list. If your firewall only allows our published IP addresses, these checks can fail and cause false DOWN alerts. We are still confirming the IP addresses used in Sydney. #### Affected IP Addresses | Country - City | Family | Old IP (published) | New IP (observed) | |---|---|---|---| | Singapore - Singapore | IPv4 | 139.162.35.94 | 172.104.47.196 | | Singapore - Singapore | IPv6 | 2400:8901:e001:56b::1 | 2400:8901::2000:efff:fec3:d889 | | Australia - Sydney | IPv4 | 172.105.167.54 | | | Australia - Sydney | IPv6 | 2400:8907:e001:303::1 | | #### Impact Only some checks from Singapore-Singapore and Sydney-Australia are affected. Other locations work normally. The published IP addresses have not changed. #### Next Update We will send an update when the issue is resolved.
- monitoring Oct 01, 2026, 08:41 AM UTC
Servers were re-attached to the original IPs. We are monitoring the situation
- resolved Oct 01, 2026, 03:22 PM UTC
The Australia-Syndey and Singapore servers were stable for the last several hours. Resolving the incident