The website isgithubcooked.com was created by an individual who wanted a way to filter GitHub’s incident history for the services and severity levels that matter to the products they build. According to the site, everyone’s reliability narrative depends on the services they rely on and the level of uptime they expect, and the tool allows users to set their own filter set to avoid talking past each other when discussing GitHub’s stability. The source data shows that GitHub has experienced 1,125 incidents since March 2016. Over the most recent three‑month period, the average has been 24 incidents per month, which represents a 5 % decrease compared with the preceding three‑month span. During that same window, the longest stretch without any recorded incident lasted eight days, ending on December 31, 2025. The worst month in the dataset was February 2026, with 37 incidents recorded. An impact breakdown provided by the site indicates that of the total incidents, 28 were classified as critical (about 2 %), 186 as major (roughly 17 %), and 911 as minor (approximately 81 %). The site also lists the worst days by count and by downtime. For example, the day with the highest number of incidents was Monday, February 9, 2026, with seven incidents, while the day with the most downtime was Wednesday, April 16, 2025, which saw 1 day and 2 hours of service interruption. Additional breakdowns show incident distribution by day of the week, with Wednesday and Tuesday each accounting for about 22 % and 21 % of all incidents, respectively. Users can click any day on the calendar view to see details such as severity level (None, Minor, Major, Critical, Ongoing) and associated downtime metrics. The site further provides charts for service uptime, downtime, and time‑to‑resolution, although those charts are noted as loading in the source text. By offering customizable filters, the tracker aims to let developers and organizations focus on the incidents that directly affect their workflows rather than relying on aggregate numbers that may mask relevant service‑specific issues.
Key facts
- GitHub has had 1125 incidents since March 2016.
- Over the last 3 months, GitHub averaged 24 incidents per month, down 5% vs previous 3 months.
- Longest streak without an incident was 8 days, ending Dec 31, 2025.
- Worst month was February 2026 with 37 incidents.
- Impact breakdown: Critical 28 (2%), Major 186 (17%), Minor 911 (81%).