GitHub header

All Systems Operational

About This Site

For the status of GitHub.com, please visit: githubstatus.com

Git Operations ? Operational
Webhooks ? Operational
API Requests ? Operational
Issues ? Operational
Pull Requests Operational
Actions ? Operational
Packages ? Operational
Pages ? Operational
Copilot Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Jul 9, 2025

No incidents reported today.

Jul 8, 2025

No incidents reported.

Jul 7, 2025

No incidents reported.

Jul 6, 2025

No incidents reported.

Jul 5, 2025

No incidents reported.

Jul 4, 2025

No incidents reported.

Jul 3, 2025
Resolved - On 7/3/2025, between 5:21:17 AM and 7:11:49 AM UTC, customers were prevented from SSO authorizing Personal Access Tokens and SSH keys via the GitHub UI. Approximately 1300 users were impacted.

A code change modified the content type of the response returned by the server, causing a lazily-loaded dropdown to fail to render, prohibiting the user from proceeding to authorize. No authorization systems were impacted during the incident, only the UI component. We mitigated the incident by reverting the code change that introduced the problem.

We are making improvements to our release process and test coverage to catch this class of error earlier in our deployment pipeline. Further, we are improving monitoring to reduce our time to detection and mitigation of issues like this one in the future.

Jul 3, 07:12 UTC
Update - The rollback has been deployed successfully on all environments. Customers should now be able to SSO authorize their Classic Personal Access Tokens and SSH keys on their GitHub organizations.
Jul 3, 07:11 UTC
Update - The root cause for the rendering bug that prevented customers from SSO authorizing Personal Access Tokens and SSH keys has started rolling out. We are continuously monitoring this rollback.
Jul 3, 06:46 UTC
Update - We have identified the root cause for the rendering bug that prevented customers from SSO authorizing Personal Access Tokens and SSH keys.The changes that caused the issue are being rolled back.
Jul 3, 06:07 UTC
Update - We are investigating an issue with SSO authorizing Classic Personal Access Tokens and SSH keys.
Jul 3, 05:45 UTC
Investigating - We are currently investigating this issue.
Jul 3, 05:39 UTC
Jul 2, 2025
Resolved - On July 2nd, 2025, between approximately 08:40 and 10:16 UTC, the Copilot service experienced degradation due to an infrastructure issue which impacted the Claude Sonnet 4 model, leading to a spike in errors. No other models were impacted.

The issue was mitigated by rebalancing load within our infrastructure. GitHub is working to further improve the resiliency of the service to prevent similar incidents in the future.

Jul 2, 10:16 UTC
Update - We are no longer experiencing degradation—Claude Sonnet 4 is once again available in Copilot Chat and across IDE integrations.

We will continue monitoring to ensure stability, but mitigation is complete.

Jul 2, 10:16 UTC
Investigating - We are currently investigating this issue.
Jul 2, 09:57 UTC
Jul 1, 2025

No incidents reported.

Jun 30, 2025
Resolved - On June 30th, 2025, between approximately 18:20 and 19:55 UTC, the Copilot service experienced a degradation of the Claude Sonnet 3.7 model due to an issue with our upstream provider. Users encountered elevated error rates when using Claude Sonnet 3.7. No other models were impacted.

The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to further improve the resiliency of the service to prevent similar incidents in the future.

Jun 30, 19:55 UTC
Update - The issues with our upstream model provider have been resolved, and Claude Sonnet 3.7 is once again available in Copilot Chat and across IDE integrations [VSCode, Visual Studio, JetBrains].
We will continue monitoring to ensure stability, but mitigation is complete.

Jun 30, 19:55 UTC
Update - We are experiencing degraded availability for the Claude 3.7 Sonnet model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue.

Other models are available and working as expected.

Jun 30, 19:14 UTC
Investigating - We are currently investigating this issue.
Jun 30, 19:13 UTC
Jun 29, 2025

No incidents reported.

Jun 28, 2025
Resolved - This incident has been resolved.
Jun 28, 01:25 UTC
Investigating - We are currently investigating this issue.
Jun 27, 12:56 UTC
Jun 27, 2025
Jun 26, 2025

No incidents reported.

Jun 25, 2025

No incidents reported.