Data source
GitHub Status
GitHub publishes its own incidents on a public status page, with history going back years. We count incidents, leaving out those marked as having no impact, and do not store or publish incident text.
Provides measurements used by the linked signal.
Counts derived from the public GitHub status page.
Visit the sourceUsed for: Major service outagesLicense: No data license published
Last 12 months277
Previous 12 months183
Major or critical86
All time1875
What the data shows
Computed from every record, as of 2026-10.
- GitHub reported 277 incidents in the last 12 months against 183 in the 12 months before: up 51%.
- 86 of the last 277 were marked major or critical, which is 31%.
- More reported incidents can mean more failures, more products or more honest reporting. These numbers cannot separate them.
Incidents per year
| Year | Incidents |
|---|---|
| 2021 | 91 |
| 2022 | 129 |
| 2023 | 160 |
| 2024 | 123 |
| 2025 | 197 |
| 2026 | 248 |
Limitations
- Incidents are self-reported, so a company that reports more honestly can look worse.
- New products add new ways to have an incident, so counts can rise without reliability getting worse.