Web, Payments, Bytes & Ventures

WPBV Radio

Tune into tech and money.

GitHub outage, 14 August 2024

The GitHub outage of 14 August 2024: what failed, why, and what GitHub changed, from its own incident report.

Provider
GitHub
Date
Duration, hours
0.6
Cause
Configuration change
Regions
Global

GitHub.com fully down after database config change (14 August 2024). The disruption lasted about 36 minutes, according to GitHub’s own timeline.

What happened. An erroneous configuration change rolled out to GitHub.com databases stopped them answering health-check pings from the routing service. The hosts were marked unhealthy, the read-only database endpoint became inaccessible, and the application couldn’t read critical data.

What changes. GitHub added guardrails to its database change management process and is prioritizing faster rollback and more resilience to dependency failures.

Questions

What caused the GitHub outage in August 2024?

An erroneous configuration change rolled out to GitHub.com databases stopped them answering health-check pings from the routing service.

Which services were affected?

All GitHub.com services.

Read how shared dependencies spread a failure in why one cloud outage can break unrelated apps, or browse the outage archive.

Started (UTC)
2024-08-14 23:02 UTC
Resolved (UTC)
2024-08-14 23:38 UTC
Services affected
All GitHub.com services
Incident report
github.blog
Sources
SourceLink
GitHub incident reporthttps://github.blog/news-insights/company-news/github-availability-report-august-2024/
WPBV Radio

What are you looking for?

Search by headline, topic or keyword.