GitHub Outage Tracker: Is GitHub Cooked?

The tracker was created because the developer wanted to filter GitHub's incident history for the services and severity levels that affect the products they build. The site lets users apply filters to see reliability from their own perspective, acknowledging that different teams depend on different parts of GitHub and expect different levels of uptime.

According to the data, GitHub has had 1,127 incidents since March 2016. Over the last three months, incidents averaged 24.7 per month, down 1% from the previous three months. The longest streak without an incident was 8 days, ending December 31, 2025, and the worst month on record was February 2026 with 37 incidents.

The site is meant to let people declare their own reliability narrative and avoid talking past each other when discussing GitHub's uptime, since each user's experience depends on their specific service usage and severity thresholds.