Uptime.com incident
Intermittent DNS resolution timeouts for HTTP checks in APAC region
Uptime.com experienced a minor incident on July 28, 2026, lasting 1d 17h. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Jul 28, 2026, 12:00 PM UTC
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)
- monitoring Jul 29, 2026, 01:14 PM UTC
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.
- investigating Jul 29, 2026, 05:20 PM UTC
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
- monitoring Jul 29, 2026, 06:09 PM UTC
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
- resolved Jul 30, 2026, 05:18 AM UTC
The issue has been resolved, no new false positives have been seen since yesterdays update