GitHub Outage Tracker: Is GitHub Cooked?
A new site, isgithubcooked.com, offers a personalized lens on GitHub's incident history, allowing developers to filter outages by specific services and severity levels. This tool empowers users to define their own 'reliability narrative,' moving beyond generic uptime statistics. It's popular on HN because it directly addresses common developer frustrations with platform reliability by providing tailored, actionable insights into service dependencies.
The Lowdown
IsGitHubCooked.com is a recently launched web application designed to help developers track GitHub's incident history with a customized view. The creator developed the site to filter GitHub's reported incidents based on the specific services and severity levels that are most relevant to their own projects.
- Personalized Reliability View: The core feature allows users to filter GitHub's incident data, enabling them to define what 'reliability' means for their specific stack and dependencies.
- Contextual Data: By tailoring the incident view, the site aims to prevent abstract discussions about GitHub's overall uptime and instead focus on how outages impact individual users.
- Incident Statistics: Since March 2016, GitHub has recorded 1125 incidents, averaging 24 incidents per month. The longest period without an incident was 8 days, and February 2026 saw the highest number of incidents at 37.
This innovative tool provides a practical way for developers to understand GitHub's operational status through their own unique perspective, facilitating more relevant assessments of platform stability for their individual needs.