GitHub Revamps Status Page to Boost Transparency

GitHub is rolling out three major changes to its status page today, aiming to give developers clearer, more accurate insights into platform health. The updates include a new incident severity level, per-service uptime percentages, and more granular disruption details for services like Copilot.

The move comes after months of reliability challenges that frustrated millions of developers. “We heard loud and clear that our previous status updates were confusing and often overstated impact,” said Sarah Chen, GitHub’s VP of Platform Reliability. “These changes are about telling the truth—even when it’s nuanced.”

New ‘Degraded Performance’ Classification

The most significant change is the addition of a Degraded Performance severity level. Previously, any incident was labeled at least a Partial Outage, even if only a small fraction of requests were affected. The new three-tier system now includes:

• Degraded Performance – Service is operational but impaired (e.g., elevated latency, intermittent errors).
• Partial Outage – Significant portion unavailable for a meaningful number of users.
• Major Outage – Broadly unavailable, affecting most users.

“Calling a small hiccup a ‘partial outage’ wasn’t honest with our users,” Chen added. “Now they’ll see exactly what level of impact to expect.” This aligns with how uptime is now calculated.

Per-Service Uptime Published on Status Page

GitHub will now display 90-day uptime percentages for each individual service directly on its status page. The calculation weights incidents by severity: Major Outages count 100% of their duration as downtime, Partial Outages count 30%, and Degraded Performance incidents count 0%.

For example, a 60-minute Partial Outage over three months would only subtract 18 minutes from the uptime metric. “This reflects actual user experience more faithfully,” said Chen. Previously, developers had to infer reliability from ambiguous incident reports.

Background

GitHub suffered several high-profile outages in early 2023, affecting Actions, Pages, and Copilot. In response, the company pledged to improve both reliability and communication. The earlier status page lacked granularity, often leaving users in the dark about which services were impacted and for how long.

Internal audits revealed that many incidents were misclassified, leading to inflated downtime figures. The new system is part of a broader “reliability investment” that includes infrastructure upgrades and automated monitoring.

What This Means for Developers

For the engineering teams that depend on GitHub, these changes reduce uncertainty. “We can now make faster decisions about whether to deploy or wait,” said Priya Patel, a senior DevOps engineer at a fintech startup. “Knowing the exact service health helps us manage our own uptime.”

The per-service uptime data will also appear in GitHub’s status page and is expected to be incorporated into enterprise SLAs. Developers using Copilot will benefit from a dedicated “Copilot AI Model Providers” component, offering clearer communication when third-party models experience issues.

GitHub plans to release further improvements by Q3, including real-time incident timelines. “This is just the beginning,” Chen noted. “We’re committed to treating status transparency as a product feature.”