GitHub Introduces Major Transparency Upgrades to Status Page

GitHub is rolling out a sweeping overhaul of its status page, introducing a new "Degraded Performance" incident severity level, publishing per-service uptime percentages, and adding a dedicated component for Copilot AI model providers. The changes, announced today, are designed to give developers more accurate and granular insights into platform health.

The upgrades come after months of reliability issues that frustrated the developer community. "We heard loud and clear that our incident communication needed to be more precise and timely," a GitHub engineering spokesperson said. "These improvements are a direct response to that feedback."

New 'Degraded Performance' State Aims for More Accurate Incident Classification

Previously, any service disruption was classified as at least a Partial Outage, even if the impact was minimal. This often misled users into thinking a service was unavailable when it was merely impaired. The new three-tier system adds a "Degraded Performance" state, which covers elevated latency, reduced functionality, or intermittent errors affecting a small percentage of requests.

"The old system didn't reflect the real user experience," the spokesperson explained. "Now, a Partial Outage means a significant portion of the service is unavailable for a meaningful number of users, while a Major Outage indicates broad unavailability. Degraded Performance fills the gap for when the service is operational but not performing optimally."

Per-Service Uptime Percentages Now Visible on Status Page

GitHub is now publishing uptime percentages for each individual service over the last 90 days directly on its status page. These percentages are calculated based on incident severity and duration, using industry-standard methods. Each severity level carries a specific downtime weight: Major Outage counts as 100% downtime, Partial Outage as 30%, and Degraded Performance as 0% (since the service remains functional).

For example, a one-hour Partial Outage would contribute only 18 minutes of effective downtime to the 90-day calculation. This nuanced approach allows developers to quickly assess each service's recent reliability track record without being misled by raw incident counts.

Granular Insights for Copilot AI Model Providers

To improve clarity around GitHub Copilot, the status page now features a dedicated "Copilot AI Model Providers" component. This provides detailed insights into the availability of third-party AI models that power Copilot features, enabling developers to distinguish between platform issues and model provider disruptions.

"AI-powered features like Copilot depend on external providers, and we want to be transparent when those services affect the experience," the spokesperson said. "This new component helps users understand exactly where the problem lies."

Background: A History of Reliability Challenges

GitHub experienced a series of high-profile outages earlier this year, prompting the company to invest heavily in reliability and communication. In a previous update, the company acknowledged that its status page lacked the granularity needed to convey the real impact of incidents. The new changes are part of a broader effort to rebuild trust with the millions of developers who depend on the platform daily.

The company has also been working behind the scenes to improve infrastructure redundancy and incident response times. These technical fixes, combined with the communication overhaul, signal a more proactive stance on availability.

What This Means for Developers and Enterprises

For individual developers, the changes mean fewer false alarms and a clearer understanding of when a service is genuinely unusable versus simply slow. Teams relying on GitHub for continuous integration and deployment can now make better-informed decisions about whether to pause work or proceed with caution.

Enterprises that pay for GitHub's premium tiers will benefit from the per-service uptime data, which can be used to meet internal SLAs or trigger automated failover procedures. The new Copilot component is especially valuable for organizations that have integrated AI coding assistants into their workflows and need to monitor third-party dependencies.

"This is a significant step forward for operational transparency," said a DevOps analyst familiar with the platform. "GitHub is finally treating its status page as a first-class communication tool, not just a static report."