GitHub
Code hosting · Official status page (opens in a new tab)
- 4Failures in GitHub's systems
- 0Its services disrupted by failures elsewhere
- Oct 21, 2018latest Nov 11, 2026Documented since
- 1 of 4Own failures with root cause confirmed
Counts cover incidents in this archive only. They are not a complete outage history or a reliability measure.
Failures in GitHub's systems
Incidents where the documented failure was in GitHub's own systems. Durations are measured to the end points the sources give.
- Nov 11, 2026GitHub: Impact across multiple GitHub products including Actions, Pages, and Copilot products.Duration: 33 minto: Provider marked resolvedResolvedUnknown · Root cause unknown
Stated cause
The provider has not stated a cause in its status updates.
- Nov 10, 2026GitHub: Incident with Git Operations and Pull RequestsDuration: 1 h 44 minto: Provider marked resolvedResolvedUnknown · Root cause unknown
Stated cause
The provider has not stated a cause in its status updates.
- Nov 9, 2026GitHub: Incident with Actions and Checks APIDuration: 47 minto: Provider marked resolvedResolvedUnknown · Root cause unknown
Stated cause
The provider has not stated a cause in its status updates.
- Oct 21, 2018GitHub outage: a 43-second network break leaves the site degraded for 24 hoursDuration: 24 h 11 minto: Status returned to greenResolvedGitHub.comWebhooksGitHub PagesNetwork equipment · Root cause confirmed
Stated cause
Routine maintenance to replace failing 100G optical equipment caused a 43-second loss of connectivity between GitHub's US East Coast network hub and its primary US East Coast data center. Database failover automation (Orchestrator) promoted West Coast databases, and writes that had not replicated had to be reconciled.