Is Uptime.com down?

We are currently experiencing connectivity issues affecting a few probe servers in our `Netherlands-Amsterdam` location. This may result in false positives, elevated latency, packet loss, or failed monitoring requests reported specifically from the Netherlands-Amsterdam monitoring location. Probe server/s affected: - ` NL-Amsterdam(IronMountain)-2` Our engineering team is investigating the issue and is working with the relevant provider to restore normal service as quickly as possible. We will share further updates as soon as more information becomes available. Should you require further assistance or have any questions, please do not hesitate to contact our support team.

Our service provider has reported an ongoing infrastructure maintenance in their Amsterdam data centre, which is impacting some servers. Their networking team is actively working to complete the maintenance and restore service to the affected systems as soon as possible. We will continue to monitor the situation closely and provide updates as we receive them. Thank you for your patience and understanding.

We’re pleased to confirm that network connectivity on the `NL-Amsterdam(IronMountain)-2` probe server has been fully restored and remains stable. The `Netherlands-Amsterdam` location is now fully operational and network connectivity is normal. Thank you for your patience. If you experience any further issues, please reach out to our support team.

HTTP checks are intermittently failing at a few APAC probe locations with DNS lookup timeouts: ``` dial tcp: lookup on x.x.x.x:53: ... i/o timeout ``` Failures are intermittent. The trigger is confirmed, the underlying cause of the dropped/slow lookups is still under investigation. Affected locations: - Japan-Tokyo - Japan-Osaka - Australia-Sydney - Singapore-Singapore (unexpectedly affected; under investigation)

The issue has been identified and addressed. We are currently monitoring the situation to ensure that checks recover and systems at the affected locations remain stable. The cause was a DNS resolver misconfiguration that led to occasional domain-name resolution failures, more frequently at geographically distant locations. This has been corrected.

The issue was only partially mitigated, while we see less domain resolution timeouts, it has not been solved completely. We are rolling out a patch to affected systems

A change affected domains resolution configuration has been rolled back. All affected checks should recover shortly. This includes an increased response time from checks executed in affected locations. The system is being actively monitored and the incident will get resolved once we ensure that the issue has been properly addressed

The issue has been resolved, no new false positives have been seen since yesterdays update

We have completed our investigation and confirm that the intermittent network connectivity issues affecting a subset of our monitoring probe locations have been resolved. Our Engineering team identified the root cause as instability on Twelve99 transit routes serving the affected locations. Connectivity over these routes has since stabilised, and both IPv4 and IPv6 connectivity are now operating normally across all previously affected probes. All monitoring locations are fully operational, and check execution has returned to normal across the network. No further action is required from customers. We apologize for any inconvenience this may have caused. Should you have any questions or continue to observe anomalies, please contact our support team.

We are currently facing connection issues with the `BO-La Paz(EdgeUno)-1` probe server. Our service provider is reporting an outage in their `La Paz - Bolivia` data centre. Our Engineering team is working closely with the provider to resolve the issue swiftly. We will provide updates as soon as they become available. Should you require further assistance or have any inquiries, please do not hesitate to contact our support team.

The `BO-La Paz(EdgeUno)-1` probe server is back Online and systems have started to stabilize. We will continue to monitor the probe server to ensure smooth operation and will collaborate with our service provider as necessary for more details.

We’re pleased to confirm that network connectivity on all affected probe server has been fully restored and remains stable. The `Bolivia-La Paz` location is fully operational and network connectivity is normal. Thank you for your patience. If you experience any further issues, please reach out to our support team.

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.