GitHub Enhances Status Page Transparency with New Incident Classification and Uptime Metrics

GitHub has announced significant enhancements to its status page communication, introducing a new incident classification system, per-service uptime metrics, and more granular insights into service disruptions. These changes, guided by principles of transparency, accuracy, and timeliness, aim to provide developers with clearer understanding of GitHub's platform health and more precise information during incidents.

A More Accurate Incident Classification System

The most notable change is the introduction of a new "Degraded Performance" incident state, creating a three-tier classification system that better reflects the spectrum of service issues:

State	What It Means
Degraded Performance	The service is operational but impaired. You may experience elevated 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.

Previously, even minor disruptions were classified as at least a partial outage, which didn't accurately reflect the actual customer impact. This often led users to believe a service was completely unavailable when it was still functional. The new classification system addresses this by providing more nuanced incident reporting.

Per-Service Uptime Metrics

GitHub is now publishing per-service uptime percentages over the last 90 days directly on its status page. These metrics are calculated based on the number of incidents, their severity, and their duration for each individual service, using industry-standard status page calculations.

The uptime calculation assigns specific downtime weights to each severity level:

• Major Outage: 100% - the full duration counts as downtime
• Partial Outage: 30% - reflects significant but not total service loss
• Degraded Performance: 0% - does not count as downtime; the service remains functional

For example, if a service experiences a 1-hour Partial Outage over a 90-day period, that would count as 18 minutes of effective downtime in the uptime calculation—not the full hour. A Degraded Performance incident, by contrast, would not affect the uptime percentage at all.

Dedicated Copilot AI Model Providers Component

GitHub has added a new component specifically for Copilot AI model providers. Previously, when a model provider experienced an outage, GitHub would declare an incident against the broader Copilot service, even when the impact was limited to a single model. This approach didn't always reflect the user experience, because many Copilot features, such as GitHub Copilot Chat and GitHub Copilot cloud agent (formerly coding agent), support multiple models.

With the new system, if one model is unavailable, users can choose an alternative model or use auto model selection to have Copilot pick the best available option. Going forward, incidents related to model availability will be reported under the new "Copilot AI Model Providers" component instead of the broader "Copilot" component. GitHub will continue to share details about which models are affected through public incident updates.

Why This Matters

These enhancements represent GitHub's commitment to transparency and effective communication, particularly when things go wrong. By providing more accurate incident classification, per-service reliability metrics, and granular insights into specific service components, GitHub is giving developers the context and details they need to make confident decisions about their operations.

As GitHub acknowledges, the platform serves as critical infrastructure for development teams worldwide. These improvements ensure that users have a clearer understanding of service health and can better assess the impact of any disruptions on their work.

Looking Ahead

These changes are part of GitHub's broader efforts to improve platform reliability and communication. Earlier this year, GitHub shared an update on recent availability issues and the work being done to address them. The new status page enhancements complement these reliability investments by ensuring that when incidents do occur, the communication around them is as clear and accurate as possible.

The introduction of the Degraded Performance state, per-service uptime metrics, and the dedicated Copilot AI Model Providers component demonstrates GitHub's ongoing commitment to transparency and its recognition that effective communication is crucial when the platform experiences issues.