Home Root causes DNS DNS Name resolution failed or returned the wrong answer.
Incidents per month
December 2025 November 2026
Incidents Major Oct 31, 04:35 UTC
Notice Sep 10, 14:34 UTC
Minor Jul 27, 20:34 UTC
Minor Jul 24, 23:03 UTC
Major Jun 23, 01:05 UTC
Minor Jun 4, 10:12 UTC
Notice May 22, 23:27 UTC
Minor May 14, 13:57 UTC
Major May 7, 15:17 UTC
Critical Apr 29, 03:23 UTC
Critical Apr 23, 16:12 UTC
On April 23, 2026, between 16:03 UTC and 17:27 UTC, multiple GitHub services experienced elevated error rates and degraded performance due to DNS resolution failures originating from our DNS infrastructure in our VA3 datacenter. Major Apr 13, 19:56 UTC
On Sunday April 13th, 2026, between 18:53 UTC and 20:30 UTC, the GitHub Pages service experienced elevated error rates. Notice Mar 27, 15:30 UTC
Critical Mar 21, 06:02 UTC
Minor Feb 23, 21:09 UTC
Major Feb 6, 01:56 UTC
Critical Dec 5, 2025, 09:03 UTC
Critical Oct 20, 2025, 07:11 UTC
Critical Oct 20, 2025, 06:48 UTC
A latent race condition in the DynamoDB DNS management system left an empty DNS record for the regional endpoint dynamodb.us-east-1.amazonaws.com, and the automation failed to repair it. Minor Jul 14, 2025, 22:56 UTC
Notice Apr 3, 2025, 11:41 UTC
Notice Feb 14, 2024, 21:57 UTC
Critical Dec 7, 2021, 10:57 UTC
Minor Apr 1, 2021, 22:11 UTC
Notice Oct 22, 2019, 22:32 UTC
Questions How common are outages caused by dns? 17 incidents in the last 12 months across the vendors tracked here were traced to dns in the vendors' own words.
How is this cause identified? From the sentences where the vendor explains why the incident happened, or by hand for landmark postmortems. Symptoms like "elevated error rates" are never counted as a cause.
Incidentsby Glyph
AWS: Increased Error Rates and Latencieslasted 15h 42mDNS