GitHub’s Enhanced Status Page: How to Interpret Degraded Performance, Per-Service Uptime, and AI Component Monitoring

Overview

GitHub powers the workflows of millions of developers, making reliability and transparent communication paramount. In response to past availability challenges, GitHub has overhauled its status page to offer clearer, more granular insights into service health. This guide explains three key updates: a new Degraded Performance incident state, per-service uptime metrics, and a dedicated component for Copilot AI Model Providers. Whether you are a DevOps engineer, a team lead, or a developer monitoring critical pipelines, understanding these changes will help you accurately assess GitHub's reliability and respond appropriately during incidents.

We’ll walk through what each change means, how to interpret the new data, and common pitfalls to avoid. By the end, you’ll be able to read the status page like a pro and make informed decisions based on real-time and historical availability.

Prerequisites

Before diving in, you should be familiar with:

• The GitHub Status Page and its basic layout.
• General concepts of uptime and downtime in SaaS platforms.
• Basic understanding of incident severity levels (e.g., partial vs. major outage).

No coding is required, but we will provide simple mathematical examples to illustrate uptime calculations.

Step-by-Step Guide to GitHub’s Status Page Upgrades

1. Understanding the New Degraded Performance State

Previously, GitHub classified any service impairment as at least a partial outage, even if the impact was minimal. This led to confusion and unnecessary alarm. Now, a three-tier system provides a more accurate spectrum of 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.

How to interpret: When you see “Degraded Performance,” your workflows might slow down or encounter occasional errors, but the service is still usable. This avoids the false impression that everything is broken. For example, if GitHub Actions runs slower than usual for 15 minutes, that’s a degraded performance, not an outage.

2. Interpreting Per-Service Uptime Percentages

GitHub now publishes uptime percentages for each service over the last 90 days directly on the status page. This allows you to quickly assess the reliability of specific components (e.g., API, Actions, Pages) rather than relying on an overall number.

How uptime is calculated:

• Each incident severity has a downtime weight:
• Major Outage: 100% of the duration counts as downtime.
• Partial Outage: 30% of the duration counts as downtime.
• Degraded Performance: 0% counts as downtime (service remains functional).

For example, if a service experienced a 1-hour Partial Outage in a 90-day period (129,600 minutes), the effective downtime is 1 hour × 30% = 18 minutes. So uptime = (129,600 - 18) / 129,600 × 100 ≈ 99.986%.

What this means for you: A single partial outage has a smaller impact on the reported uptime than you might think. Don’t be alarmed by a 99.9% number; check the specific incident history to see actual severity and frequency. Use the per-service metrics to decide which GitHub services meet your internal availability requirements.

3. Exploring the AI Model Providers Component

Copilot is a critical AI tool for many developers. GitHub has introduced a dedicated Copilot AI Model Providers component on the status page. This gives you granular insight into availability issues with the underlying AI models (e.g., OpenAI’s models) that power Copilot suggestions.

Previously, any model provider degradation was lumped into a generic “Copilot” status. Now you can see if the issue is with a specific provider, such as a latency spike in the Azure OpenAI endpoint. This helps you determine whether to retry, switch to a fallback, or wait for resolution.

How to use it: If you experience Copilot slowdowns, check this component for a “Degraded Performance” or “Partial Outage” badge. If it’s green, the problem may be on your side (e.g., network). If it shows an issue, you can trust that GitHub is aware and working on it.

Common Mistakes to Avoid

❌ Mistaking Degraded Performance for an Outage

Many users see any non-green status and assume the service is completely down. Degraded Performance means the service is still usable, just not at peak performance. Only treat it as a serious issue if your workflow is critically dependent on low latency or zero errors.

❌ Ignoring Per-Service Uptime in Favor of an Overall Number

The overall status page “uptime” is an aggregate. For example, GitHub’s overall uptime might be 99.99%, but the API could have had a partial outage that affected your automations. Always click into individual services to see their specific uptime and incident log.

❌ Overlooking the Copilot AI Component

If Copilot is slow or unresponsive, don’t immediately blame your IDE or network. Check the Copilot AI Model Providers component on the status page. A “Degraded Performance” there could explain intermittent suggestions without any other service degradation.

❌ Misinterpreting Uptime Percentages

A single partial outage (weighted at 30% of its duration) can still result in a 99.9%+ uptime over 90 days. A high uptime percentage does not mean zero incidents; it means incidents were short-lived or low-severity. Always review the incident history for context.

Summary

GitHub’s enhanced status page brings more transparency through three key changes:

• Degraded Performance – a new severity level that accurately reflects minor impairments without causing panic.
• Per-service uptime percentages – allowing you to evaluate each component’s reliability over the last 90 days.
• Copilot AI Model Providers component – providing granular visibility into third-party AI model availability.

By understanding these updates, you can now make more informed decisions about your reliance on GitHub services, communicate better with your team during incidents, and set realistic expectations for uptime and performance. Remember to always check the specific component relevant to your workflow and to interpret “Degraded Performance” as a warning, not a crisis.

For the latest information, visit the GitHub Status Page.