GitHub, the platform where millions of developers collaborate on critical projects, has long recognized the importance of transparent and timely communication regarding service health. Following earlier discussions about availability challenges and reliability investments, the company is now rolling out three key updates to its status page. These changes aim to provide developers with more accurate incident information, clearer historical performance data, and deeper visibility into specific services.
A More Accurate Incident Classification System
Previously, GitHub used only two severity levels: Partial Outage and Major Outage. This binary system often misrepresented the actual user impact, as even minor issues—such as elevated latency or occasional errors—were labeled as outages. To address this, GitHub is introducing a new severity level called Degraded Performance.
The new three-tier classification now includes:
- Degraded Performance – The service remains operational but is impaired. Users may experience higher latency, reduced functionality, or intermittent errors affecting a small percentage of requests.
- Partial Outage – A significant portion of the service is unavailable or severely impacted for a meaningful number of users.
- Major Outage – The service is broadly unavailable, affecting most or all users.
This refined system ensures that incidents are classified based on their true severity, giving users a more precise understanding of what is happening. No longer will a minor slowdown be mistakenly reported as a full-blown outage, reducing unnecessary alarm and improving trust in the status page.
Per-Service Uptime Metrics Now Visible
Another major enhancement is the publication of per-service uptime percentages directly on the GitHub status page. Users can now view the 90-day uptime record for each individual service—such as Actions, Packages, or Copilot—allowing for quick assessment of recent reliability.
These percentages are calculated based on the number, severity, and duration of incidents affecting each service. The methodology follows industry standards but uses specific downtime weights:
| Severity | Downtime Weight |
|---|---|
| Major Outage | 100% – the entire duration counts as downtime |
| Partial Outage | 30% – reflects significant but not total service loss |
| Degraded Performance | 0% – does not count as downtime since the service remains functional |
For example, if a service experienced a one-hour Partial Outage over 90 days, that would contribute only 18 minutes of effective downtime to the uptime calculation—not the full hour. A Degraded Performance incident, though communicated to users, does not affect the uptime percentage. This approach ensures that the numbers accurately reflect true availability rather than penalizing for minor impairments.
Granular Insights for Specific Services
To further improve communication during incidents, GitHub is rolling out more detailed component information. The first example is a dedicated “Copilot AI Model Providers” component on the status page. This allows users to see exactly which third-party model provider is experiencing issues, rather than a generic “Copilot” status. Similar granularity will be extended to other services over time, helping developers troubleshoot and plan more effectively.
These changes reflect GitHub's commitment to transparency, accuracy, and timeliness. By providing clearer incident classifications, publishing service-level uptime metrics, and offering deeper insights into specific components, the platform empowers developers to make informed decisions and maintain confidence in their workflows.
For more details, visit the GitHub Status Page.