Uptime.com incident
Intermittent DNS checks failures in Austria Vienna
Resolved after 1 hour 47 minutes, on August 10, 2026.
DNS checks on affected nodes were delayed or did not execute, and dependent alerts may not have been delivered. If you rely on DNS monitoring for alerting, treat that window as having incomplete coverage. We have added capacity to affected regions and reduced per-node execution concurrency, which restored normal check execution. A permanent fix for the underlying defect is in progress, and we are adding capacity limits and monitoring to detect this class of failure earlier. Any other alerts originating from other checks are affected by outdated IP white listing rules announced on August 2
Update timeline
- monitoring Aug 10, 2026, 01:12 PM UTC
DNS checks on affected nodes were delayed or did not execute, and dependent alerts may not have been delivered. If you rely on DNS monitoring for alerting, treat that window as having incomplete coverage. We have added capacity to affected regions and reduced per-node execution concurrency, which restored normal check execution. A permanent fix for the underlying defect is in progress, and we are adding capacity limits and monitoring to detect this class of failure earlier. Any other alerts originating from other checks are affected by outdated IP white listing rules announced on August 2
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