Skip to content
GitHub · Developer toolsApr 13, 2026, 19:56 UTC

Incident with Pages

MajorDNSUpdated 16h ago
Apr 13, 19:56 UTCApr 13, 20:35 UTC
Duration
39m
Impact
Major
Root cause
DNS
GitHub, 90 days
68 incidents
Affected
Not listed by the vendor.

What happened

On Sunday April 13th, 2026, between 18:53 UTC and 20:30 UTC, the GitHub Pages service experienced elevated error rates. On average, the error rate was 10.58% and peaked at 12.77% of requests to the service, resulting in approximately 17.5 million failed requests returning HTTP 500 errors. This was due to an automated DNS management tool (octodns) erroneously deleting a DNS record for a Pages backend storage host after its upstream data source intermittently failed to return the record, causing the tool to treat it as stale and remove it. We mitigated the incident by re-creating the deleted DNS record. To prevent future incidents, we are implementing availability-zone-tolerant routing in the Pages frontend so that an unresolvable backend host triggers failover to healthy hosts rather than returning errors, adding safeguards to prevent automated deletion of DNS records owned by other systems, and improving logging and alerting for DNS resolution failures in the Pages serving path.

Timeline

  1. Resolved · Apr 13, 20:35 UTC
    On Sunday April 13th, 2026, between 18:53 UTC and 20:30 UTC, the GitHub Pages service experienced elevated error rates. On average, the error rate was 10.58% and peaked at 12.77% of requests to the service, resulting in approximately 17.5 million failed requests returning HTTP 500 errors. This was due to an automated DNS management tool (octodns) erroneously deleting a DNS record for a Pages backend storage host after its upstream data source intermittently failed to return the record, causing the tool to treat it as stale and remove it. We mitigated the incident by re-creating the deleted DNS record. To prevent future incidents, we are implementing availability-zone-tolerant routing in the Pages frontend so that an unresolvable backend host triggers failover to healthy hosts rather than returning errors, adding safeguards to prevent automated deletion of DNS records owned by other systems, and improving logging and alerting for DNS resolution failures in the Pages serving path.

More from GitHub

Full history
StartedIncidentDuration
Sep 2310:11 UTCIncident across several servicesOngoing
Sep 2022:13 UTCIncident with Pull Requests1h 9m
Sep 1720:59 UTCElevated rate of errors for OpenAI models provided by Copilot50m
Sep 1607:20 UTCDegradation with Gemini 3.8 Flash10h 28m
Sep 1519:11 UTCDisruption with some GitHub services49m
Sep 1509:47 UTCDisruption with some GitHub services1h 30m

Also caused by dns

All
StartedIncidentDuration
Jul 2720:34 UTCDelays in creation of DNS recordsSupabase2h 2m
Jun 2301:05 UTCINC20000046Snowflake1h 30m
Jun 410:12 UTCDNS API ServiceDigitalOcean1h 35m
May 2223:27 UTCNew Database Creation Failing Due to Upstream Provider IssueUpstash32m
May 1413:57 UTCDNS service, Certificates and Managed MongoDBDigitalOcean6h 49m
May 715:17 UTCAWS Cluster DNS Changes Degraded PerformanceMongoDB6h 58m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.