GitHub Overhauls Status Page with New Degraded Performance Tier and Per-Service Uptime Metrics

By ✦ min read

<h2>Breaking: GitHub Revamps Status Page to Improve Transparency During Service Disruptions</h2><p>GitHub announced today a series of major updates to its status page, introducing a new <strong>Degraded Performance</strong> severity level and publishing per-service uptime statistics for the first time. The changes, effective immediately, aim to give developers clearer, more accurate information about platform health and incident impact.</p><figure style="margin:20px 0"><img src="https://github.blog/wp-content/uploads/2024/06/AI-DarkMode-4.png?resize=800%2C425" alt="GitHub Overhauls Status Page with New Degraded Performance Tier and Per-Service Uptime Metrics" style="width:100%;height:auto;border-radius:8px" loading="lazy"><figcaption style="font-size:12px;color:#666;margin-top:5px">Source: github.blog</figcaption></figure><p>“Developers rely on GitHub to build and ship code,” said a company spokesperson. “These updates ensure that when something goes wrong, we communicate the exact nature and scope of the issue—no more, no less.” The moves come after earlier promises to improve reliability and incident communication.</p><h3 id="degraded-performance">New &lsquo;Degraded Performance&rsquo; Tier Improves Incident Classification</h3><p>GitHub’s status page previously offered only two severity levels: <em>Partial Outage</em> and <em>Major Outage</em>. Now a third tier—<strong>Degraded Performance</strong>—sits between them, capturing situations where a service is operational but impaired.</p><p>“In the past, even minor latency or intermittent errors were labeled as a partial outage,” the spokesperson said. “This misled users into thinking the service was down when it was still usable. The new tier fixes that.” Degraded Performance covers elevated latency, reduced functionality, or errors affecting a small percentage of requests—without counting as downtime in uptime calculations.</p><h3 id="uptime-metrics">Per-Service Uptime Metrics Now Public</h3><p>For the first time, GitHub is publishing <strong>90-day uptime percentages for each individual service</strong> directly on the status page. Users can quickly see the recent reliability track record of services like Actions, Copilot, Issues, and more.</p><p>The uptime calculation uses weighted downtime: <em>Major Outage</em> counts 100% of duration; <em>Partial Outage</em> counts 30%; and <em>Degraded Performance</em> counts 0%. For example, a 1-hour Partial Outage results in 18 minutes of effective downtime. “This gives a more honest picture of service health,” the spokesperson noted.</p><h3 id="copilot-component">Granular Insights for Copilot AI Model Providers</h3><p>GitHub is also launching a dedicated <strong>Copilot AI Model Providers</strong> component on the status page. This component will provide clearer communication about availability issues affecting the underlying AI models that power GitHub Copilot.</p><figure style="margin:20px 0"><img src="https://github.blog/wp-content/uploads/2024/05/Enterprise-DarkMode-3.png?resize=800%2C425" alt="GitHub Overhauls Status Page with New Degraded Performance Tier and Per-Service Uptime Metrics" style="width:100%;height:auto;border-radius:8px" loading="lazy"><figcaption style="font-size:12px;color:#666;margin-top:5px">Source: github.blog</figcaption></figure><p>“Previously, a model provider outage could be conflated with a broader Copilot issue,” the spokesperson explained. “Now we can isolate and communicate the exact provider impact.” This is part of a broader effort to offer <em>more granular insights</em> into service disruptions.</p><h2>Background: Why These Changes Matter</h2><p>GitHub has faced scrutiny over the past year due to several high-profile availability incidents. In response, the company invested heavily in infrastructure reliability and pledged to improve incident communication. The old status page classified all disruptions as partial outages, eroding trust.</p><p>“We heard loud and clear that developers wanted more nuance,” the spokesperson said. “A simple ‘up or down’ binary wasn’t enough.” The new system aligns with industry best practices for status page transparency.</p><h2>What This Means for Developers</h2><p>Developers can now make smarter decisions during incidents: a <em>Degraded Performance</em> label means they can likely continue working, while a <em>Major Outage</em> signals a critical break. The per-service uptime data enables engineering teams to assess GitHub’s reliability for their specific workflows.</p><p>Long term, these changes set a higher bar for <strong>transparency</strong> across the industry. “We’re committed to being clear about our platform’s health,” the spokesperson added. “This is just the beginning of ongoing improvements.”</p>