Bringing more transparency to GitHub’s status page
- GitHub 状态页新增事件详细时间线和影响组件说明
- 用户可查看每起事件的具体恢复步骤和根本原因
- 改进旨在提升平台可靠性沟通和开发者信任
Bringing more transparency to GitHub’s status page - The GitHub Blog
Skip to contentSkip to sidebar
[](https://github.com/)/Blog
Try GitHub CopilotSee what's new
Learn about artificial intelligence and machine learning across the GitHub ecosystem and the wider industry.
Learn how to build with generative AI.
Change how you work with GitHub Copilot.
Everything developers need to know about LLMs.
Machine learning tips, tricks, and best practices.
Explore the capabilities and benefits of AI code generation and how it can improve your developer experience.
Learn more
Resources for developers to grow in their skills and careers.
Insights and best practices for building apps.
Tips & tricks to grow as a professional developer.
Improve how you use GitHub at work.
Learn how to move into your first professional role.
Stay current on what’s new (or new again).
Learn how to start building, shipping, and maintaining software with GitHub.
Learn more
Get an inside look at how we’re building the home for all developers.
Discover how we deliver a performant and highly available experience across the GitHub platform.
Explore best practices for building software at scale with a majority remote team.
Get a glimpse at the technology underlying the world’s leading AI-powered developer platform.
Learn how we build security into everything we do across the developer lifecycle.
Find out what goes into making GitHub the home for all developers.
Our engineering and security teams do some incredible work. Let’s take a look at how we use GitHub to be more productive, build collaboratively, and shift security left.
Learn more
Explore how to write, build, and deploy enterprise software at scale.
Automating your way to faster and more secure ships.
Guides on continuous integration and delivery.
Tips, tools, and tricks to improve developer collaboration.
DevOps resources for enterprise engineering teams.
How to integrate security into the SDLC.
Ensuring your builds stay clean.
Learn why Gartner positioned GitHub as a Leader for the second year in a row.
Learn more
Keep up with what’s new and notable from inside GitHub.
An inside look at news and product updates from GitHub.
The latest on GitHub’s platform, products, and tools.
Insights into the state of open source on GitHub.
The latest policy and regulatory changes in software.
Data-driven insights around the developer ecosystem.
Older news and updates from GitHub.
Learn how to use retrieval-augmented generation (RAG) to capture more insights.
Learn more
Everything open source on GitHub.
The latest Git updates.
Spotlighting open source maintainers.
How open source is driving positive change.
Explore open source games on GitHub.
Organizations worldwide are incorporating open source methodologies into the way they build and ship their own software.
Learn more
Stay up to date on everything security.
Application security, explained.
Demystifying supply chain security.
Updates from the GitHub Security Lab.
Helpful tips on securing web applications.
Learn about core challenges in DevSecOps, and how you can start addressing them with AI and automation.
Learn more
Search
Categories
Learn about artificial intelligence and machine learning across the GitHub ecosystem and the wider industry.
Learn how to build with generative AI.
Change how you work with GitHub Copilot.
Everything developers need to know about LLMs.
Machine learning tips, tricks, and best practices.
Explore the capabilities and benefits of AI code generation and how it can improve your developer experience.
Resources for developers to grow in their skills and careers.
Insights and best practices for building apps.
Tips & tricks to grow as a professional developer.
Improve how you use GitHub at work.
Learn how to move into your first professional role.
Stay current on what’s new (or new again).
Learn how to start building, shipping, and maintaining software with GitHub.
Get an inside look at how we’re building the home for all developers.
Discover how we deliver a performant and highly available experience across the GitHub platform.
Explore best practices for building software at scale with a majority remote team.
Get a glimpse at the technology underlying the world’s leading AI-powered developer platform.
Learn how we build security into everything we do across the developer lifecycle.
Find out what goes into making GitHub the home for all developers.
Our engineering and security teams do some incredible work. Let’s take a look at how we use GitHub to be more productive, build collaboratively, and shift security left.
Explore how to write, build, and deploy enterprise software at scale.
Automating your way to faster and more secure ships.
Guides on continuous integration and delivery.
Tips, tools, and tricks to improve developer collaboration.
DevOps resources for enterprise engineering teams.
How to integrate security into the SDLC.
Ensuring your builds stay clean.
Learn why Gartner positioned GitHub as a Leader for the second year in a row.
Keep up with what’s new and notable from inside GitHub.
An inside look at news and product updates from GitHub.
The latest on GitHub’s platform, products, and tools.
Insights into the state of open source on GitHub.
The latest policy and regulatory changes in software.
Data-driven insights around the developer ecosystem.
Older news and updates from GitHub.
Learn how to use retrieval-augmented generation (RAG) to capture more insights.
Everything open source on GitHub.
The latest Git updates.
Spotlighting open source maintainers.
How open source is driving positive change.
Explore open source games on GitHub.
Organizations worldwide are incorporating open source methodologies into the way they build and ship their own software.
Stay up to date on everything security.
Application security, explained.
Demystifying supply chain security.
Updates from the GitHub Security Lab.
Helpful tips on securing web applications.
Learn about core challenges in DevSecOps, and how you can start addressing them with AI and automation.
See what's newTry GitHub Copilot
Home/News & insights/Company news
Bringing more transparency to GitHub’s status page
Changes to the status page will provide more specific data, so you’ll have better insight into the overall health of the platform.
[Jakub Oleksy](https://github.blog/author/jakuboleksy/ "Posts by Jakub Oleksy")·@jakuboleksy
April 17, 2026
| 4 minutes
- Share:
- [](https://x.com/share?text=Bringing%20more%20transparency%20to%20GitHub%E2%80%99s%20status%20page&url=https%3A%2F%2Fgithub.blog%2Fnews-insights%2Fcompany-news%2Fbringing-more-transparency-to-githubs-status-page%2F)
- [](https://www.facebook.com/sharer/sharer.php?t=Bringing%20more%20transparency%20to%20GitHub%E2%80%99s%20status%20page&u=https%3A%2F%2Fgithub.blog%2Fnews-insights%2Fcompany-news%2Fbringing-more-transparency-to-githubs-status-page%2F)
- [](https://www.linkedin.com/shareArticle?title=Bringing%20more%20transparency%20to%20GitHub%E2%80%99s%20status%20page&url=https%3A%2F%2Fgithub.blog%2Fnews-insights%2Fcompany-news%2Fbringing-more-transparency-to-githubs-status-page%2F)
GitHub is where millions of developers do their most important work, and that comes with a responsibility we take seriously. Earlier this year, we shared an update on GitHub’s recent availability issues and the work we’re doing to address them. Alongside those reliability investments, we have prioritized improving how we communicate during and after incidents, increasing the specificity of the data we provide and giving better insight into the platform’s health overall.
Guided by transparency, accuracy, and timeliness, we’re rolling out three changes to how we communicate service health—outlined below.
- A new **“Degraded Performance”** state for more accurate incident classification
- **Per-service uptime metrics** published for each service
- More granular insights on service disruptions, starting with a dedicated **“Copilot AI Model Providers”** component for clearer communication around model provider availability
Improving accuracy
We’re adding a new incident severity level: **Degraded Performance**. This sits alongside our existing Partial Outage and Major Outage states, creating a three-tier system that more accurately reflects the spectrum of issues that can affect GitHub services.
| 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 with minimal service disruption, all incidents were classified at least as a partial outage. This did not accurately reflect customer impact and led users to believe a service was unavailable even if it was still functional.
Per-service uptime on the status page
We are now publishing **per-service uptime percentages** over the last 90 days directly on our status page, so you can quickly understand each service’s recent reliability track record.
These uptime percentages are calculated based on the number of incidents, their severity, and their duration for each individual service. These calculations are based on industry standard status page calculations.
Each severity level carries a specific downtime weight:
| **Severity** | **Downtime weight** | | --- | --- | | **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 experienced 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.
Insights on model provider service disruptions
We’ve added a new component representing Copilot AI model providers.
Previously, when a model provider experienced an outage, we declared an incident against the Copilot service, even when the impact was limited to a single model. That didn’t always reflect your experience, because many Copilot features, such as GitHub Copilot Chat and GitHub Copilot cloud agent (formerly coding agent) support multiple models. On those features, if one model is unavailable, you can choose an alternative model or use auto model selection to have Copilot pick the best available option for you.
Going forward, incidents related to model availability will be reported under the new **“Copilot AI Model Providers”** component instead of the broader “Copilot” component. We’ll continue to share details, such as which models are affected, through public incident updates.
Our continued commitment to transparency
We recognize that clear communication and transparency matter most when things go wrong. The **Degraded Performance** state, **per-service uptime percentages**, and dedicated **Copilot AI Model Providers** component are designed to give you the context and details you need to make confident decisions about your operations.
We know GitHub is critical infrastructure for your teams, and we are committed to ensuring our platform is available when and where you need it; and communicating effectively and transparently when it is not.
Written by
[Jakub Oleksy](https://github.blog/author/jakuboleksy/)
Table of Contents
- Improving accuracy
- Per-service uptime on the status page
- Insights on model provider service disruptions
- Our continued commitment to transparency
Related posts
[Developer policy update: Intermediary liability, copyright, and transparency](https://github.blog/news-insights/policy-news-and-insights/developer-policy-update-intermediary-liability-copyright-and-transparency/)
We’re sharing recent policy updates that developers should know about, updating our Transparency Center with the full year of 2025 data, and looking to what’s ahead.
[Margaret Tucker](https://github.blog/author/margarettucker/ "Posts by Margaret Tucker")
[GitHub availability report: March 2026](https://github.blog/news-insights/company-news/github-availability-report-march-2026/)
In March, we experienced four incidents that resulted in degraded performance across GitHub services.
[Jakub Oleksy](https://github.blog/author/jakuboleksy/ "Posts by Jakub Oleksy")
[GitHub Universe is back: We want you to take the stage](https://github.blog/news-insights/company-news/github-universe-is-back-we-want-you-to-take-the-stage/)
Get inspired by five of the most memorable, magical, and quirky Universe sessions to date.
[Rachel Cohen](https://github.blog/author/rachcoheller/ "Posts by Rachel Cohen")
Explore more from GitHub
Docs
Everything you need to master GitHub, all in one place.
GitHub
Build what’s next on GitHub, the place for anyone from anywhere to build anything.
Customer stories
Meet the companies and engineering teams that build with GitHub.
The GitHub Podcast
Catch up on the GitHub podcast, a show dedicated to the topics, trends, stories and culture in and around the open source developer community on GitHub.
We do newsletters, too
Discover tips, technical guides, and best practices in our biweekly newsletter just for devs.
Your email address
*Your email address
Subscribe
- [x] Yes please, I’d like GitHub and affiliates to use my information for personalized communications, targeted advertising and campaign effectiveness. See the GitHub Privacy Statement for more details.
Subscribe
Site-wide Links
[](https://github.com/)
Product
Platform
Support
Company
- GitHub on LinkedIn
- GitHub on Instagram
- GitHub on YouTube
- GitHub on X
- GitHub on TikTok
- GitHub on Twitch
- GitHub’s organization on GitHub
!Image 24×
问问这篇内容
回答仅基于本篇材料Skill 包
领域模板，一键产出结构化笔记论文精读包
把一篇论文 / 技术博客精读成结构化笔记：问题、方法、实验、批判、延伸阅读。
- · TL;DR（1 段）
- · 研究问题与动机
- · 方法概览
投融资雷达包
把一条融资 / 创投新闻整理成投资人视角的雷达卡：交易要点、判断、竞争格局、风险、尽调清单。
- · 交易要点（公司 / 轮次 / 金额 / 投资人 / 估值，材料未明示则写 “未披露”）
- · 投资 thesis（这家公司为什么值得关注）
- · 竞争格局与替代方案