GitHub Outage History

We are investigating reports of degraded availability for API Requests, Issues, Pages and Pull Requests

Actions is experiencing degraded performance. We are continuing to investigate.

We're seeing increased database replication delays on collab which is causing increased error rates in authorization endpoints and follow-on increased error rates across the system - we are investigating

We have reduced load on this cluster with internal load-shedding and are seeing signs of recovery but continue to monitor

Pull Requests is experiencing degraded performance. We are continuing to investigate.

We are investigating reports of impacted performance for some GitHub services.

We are investigating reports of impacted performance for some GitHub services.

Some users may be experiencing failures when using Copilot code review. We have identified the root cause and are working on a mitigation.

We are applying the mitigation and expect recovery within approximately 30 minutes.

We are investigating reports of degraded performance for Copilot AI Model Providers

We are experiencing degraded availability for the Grok 4.6 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.

The Grok 4.5 model has degraded availability as well. We are working with the upstream provider to resolve the issue.

The issues with our upstream model provider have been resolved, and Grok models are once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability, but mitigation is complete.

We are investigating reports of degraded performance for Pull Requests

Diffs in the PR view may be stale for several minutes. We are investigating and scaling up resources.

Time to update pull request diffs have improved to normal thresholds.

We are investigating reports of degraded performance for Copilot AI Model Providers

Copilot is experiencing a higher rate of errors for OpenAI models, including gpt-5.2, gpt-5.3-codex, gpt-5.4, gpt-5.4, and the gpt-5.6 family of models. Other models are not impacted.

One of our model providers has confirmed an incident on their end. We have provided them details to help identify the issue. We are starting to see recovery.

We are investigating reports of degraded availability for Copilot AI Model Providers

We are experiencing degraded availability for the Kimi K3 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.

Copilot AI Model Providers is experiencing degraded performance. We are continuing to investigate.

The issues with our upstream model provider have been mitigated, and Kimi K3 is once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability.

We are investigating reports of impacted performance for some GitHub services.

We are currently investigating increased errors with billing services. Customers may observe failed billing budget page loads, and users of the Copilot CLI may observe failures starting or continuing sessions.

We've applied a mitigation to unblock Copilot usage and have observed recovery for this particular impact. We're continuing to investigate and apply mitigations for the billing page disruption while monitoring to ensure Copilot remains recovered.

We are continuing to monitor the mitigation that we have applied for the billing page disruption.

Our mitigation is still holding as we continue to investigate to find the root cause.

Our mitigation continues to hold, and service conditions remain stable. We are continuing to investigate the concentrated workload responsible for the issue and are preparing additional preventative improvements. We have not identified a material change in customer impact since the previous update. We will provide another update as the investigation progresses.

No material change since the previous update. Service conditions remain stable following the mitigation, and we have not observed any further customer impact. We are actively monitoring the service while implementing targeted fixes to address the underlying root cause.

We are investigating reports of degraded performance for Actions and Pull Requests

We are investigating elevated delays and timeouts affecting Actions workflow runs triggered by pull request events. 20% of actions runs have delayed starts of more than 5 minutes and up to 4% of runs failed to trigger. We are actively working on mitigation and will provide updates as we learn more.

We've applied mitigations and are seeing recovery in Actions workflow runs and blocked pull request merges. We're continuing to monitor for sustained health of merge commit creates before resolving.

We confirmed full recovery beginning at 23:58 UTC. Actions workflow runs and pull request merges are operating normally. We will now resolve the incident while continuing to monitor service health.

We are investigating reports of impacted performance for some GitHub services.

We are investigating reports of degraded performance for Actions

Failures while queuing and running Actions jobs for a subset of customers are now resolving. We are monitoring for full recovery.

We are investigating reports of degraded availability for Copilot AI Model Providers

We are experiencing degraded availability for the Fable model in Copilot products and IDE surfaces. This is due to an issue with the upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.

We are investigating reports of impacted performance for some GitHub services.

We are investigating reports of impacted performance for some GitHub services.

GHEC Team Sync is currently degraded for enterprises with personal accounts, causing delays when syncing teams to IdP groups. We have identified the cause of the delays and are working on a mitigation. We will provide an update on our progress at 20:00 UTC.

We have deployed a mitigation. At this time GHEC Team Sync has recovered for enterprises with personal accounts. Teams syncing to IdP groups have returned to their normal cadence.

We are investigating reports of degraded performance for Copilot AI Model Providers

We are experiencing degraded availability for the Fable 5 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.

We are seeing modest recovery, but are still experiencing degraded availability for the Fable 5 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.

The issues with our upstream model provider have been resolved, and Fable 5 is once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability, but mitigation is complete.

We are investigating reports of impacted performance for some GitHub services.

We are investigating issues with Login and when downloading Release Assets. We will continue to keep users updated on progress towards mitigation.

We have identified the root cause and are working on mitigation. Errors on the login page and downloading release assets have decreased, but we are not fully mitigated. We will continue to provide updates.

We are investigating reports of degraded performance for Issues and Pull Requests

We are investigating reports of errors affecting Pull Requests and Issues on GitHub.com. Some users may encounter 500 errors when loading pull request and issue pages. Our engineering teams are actively investigating the root cause, which appears to be related to a database infrastructure issue. We will provide an update as soon as we have more information.

We are investigating reports of degraded performance for API Requests

We are investigating reports of a small increase in error rates affecting GraphQL API requests. We are working on increasing capacity and continue to investigate the increased errors. We will provide another update when we have more information

We have returned to a healthy baseline on GraphQL API requests. We will continue to work on investigations into the errors seen during this incident.

We are investigating reports of impacted performance for some GitHub services.

We are investigating reports of impacted performance for some GitHub services.

We are investigating reports of users being unable to create fine-grained Personal Access Tokens. Attempting to create a new token redirects the user back to the token overview page without an error message, but the token was not created.