Get email notifications whenever GitHub creates, updates or resolves an incident.
Get text message notifications whenever GitHub creates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get webhook notifications whenever GitHub creates an incident, updates an incident, resolves an incident or changes a component status.
Visit our support site.
All Systems Operational
About This Site
For the status of GitHub Enterprise Cloud - EU, please visit: eu.githubstatus.com
For the status of GitHub Enterprise Cloud - Australia, please visit: au.githubstatus.com
For the status of GitHub Enterprise Cloud - US, please visit: us.githubstatus.com
Git Operations
?
Operational
Webhooks
?
Operational
Visit www.githubstatus.com for more information
Operational
API Requests
?
Operational
Issues
?
Operational
Pull Requests
?
Operational
Actions
?
Operational
Packages
?
Operational
Pages
?
Operational
Codespaces
?
Operational
Copilot
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jul 14, 2025
No incidents reported today.
Jul 13, 2025
No incidents reported.
Jul 12, 2025
No incidents reported.
Jul 11, 2025
No incidents reported.
Jul 10, 2025
No incidents reported.
Jul 9, 2025
No incidents reported.
Jul 8, 2025
Resolved -
On July 8, 2025, between 14:20 UTC and 16:30 UTC, GitHub Actions service experienced degraded performance leading to delays in updates to Actions workflow runs including missing logs and delayed run status. During this period, 1.07% of Actions workflow runs experienced delayed updates, while 0.34% of runs completed, but showed as canceled in their status. The incident was caused by imbalanced load in our underlying service infrastructure. The issue was mitigated by scaling up our services and tuning resource thresholds. We are working to improve our resilience to load spikes, capacity planning to prevent similar issues, and are implementing more robust monitoring to reduce detection and mitigation time for similar incidents in the future.
Jul 8, 16:44 UTC
Jul 8, 16:44 UTC
Update -
We are seeing complete recovery for Actions. New jobs will run as normal. Some runs initiated during the incident will be left in a stuck state and will not complete.
Jul 8, 16:43 UTC
Jul 8, 16:43 UTC
Update -
We have scaled out our capacity and customers will begin to see timely updates.
Jul 8, 16:29 UTC
Jul 8, 16:29 UTC
Update -
Some customers are seeing delays in updates to their runs resulting in missing logs and delayed run status updates. We are investigating the cause of the issue.
Jul 8, 16:10 UTC
Jul 8, 16:10 UTC
Investigating -
We are investigating reports of degraded performance for Actions
Jul 8, 16:05 UTC
Jul 8, 16:05 UTC
Jul 7, 2025
Resolved -
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Jul 7, 22:34 UTC
Jul 7, 22:34 UTC
Update -
We are investigating reports of Copilot Coding Agent service degraded performance
Jul 7, 22:31 UTC
Jul 7, 22:31 UTC
Investigating -
We are currently investigating this issue.
Jul 7, 22:29 UTC
Jul 7, 22:29 UTC
Resolved -
On July 7th, 2025, between 18:20 UTC and 22:10 UTC the Actions service was degraded for GitHub Larger Hosted and scale set runners. During this time window, 9% of GitHub Larger Hosted Runners and scale set jobs saw a delay of at least 5 minutes before being assigned to a runner. Impact was more apparent to customers that didn’t have pre-scaled runner pools or who infrequently queued jobs during the incident window. This was due to a change that unintentionally decreased the rate at which we notified our backend that new scale set runners were coming online, and was mitigated by reverting that change. To reduce the likelihood and impact time of a similar issue in the future, we are improving our detection of this failure mode so we catch it in earlier stages of development and rollout.
Jul 7, 22:22 UTC
Jul 7, 22:22 UTC
Update -
We are investigating reports of degraded performance for larger runners.
Jul 7, 22:07 UTC
Jul 7, 22:07 UTC
Investigating -
We are currently investigating this issue.
Jul 7, 22:03 UTC
Jul 7, 22:03 UTC
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 3:22 AM and 7:12 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
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
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
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
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
Jul 3, 05:45 UTC
Investigating -
We are currently investigating this issue.
Jul 3, 05:39 UTC
Jul 3, 05:39 UTC
Jul 2, 2025
Resolved -
On July 2, 2025, between 1:35 AM UTC and 16:23 UTC, the GitHub Enterprise Importer (GEI) migration service experienced degraded performance and slower-than-normal migration queue processing times. This incident was triggered due to a migration including an abnormally large number of repositories, overwhelming the queue and slowing processing for all migrations.
We mitigated the incident by removing the problematic migrations from the queue. Service was restored to normal operation as the queue volume was reduced.
To ensure system stability, we have introduced additional concurrency controls that limit the number of queued repositories per organization migration, helping to prevent similar incidents in the future.
Jul 2, 16:23 UTC
We mitigated the incident by removing the problematic migrations from the queue. Service was restored to normal operation as the queue volume was reduced.
To ensure system stability, we have introduced additional concurrency controls that limit the number of queued repositories per organization migration, helping to prevent similar incidents in the future.
Jul 2, 16:23 UTC
Update -
We're down to healthy level of queued migrations and the system is processing migrations at normal system concurrency levels.
Jul 2, 16:23 UTC
Jul 2, 16:23 UTC
Update -
Repository migrations are experiencing delayed processing times. Mitigation has been implemented and migration times are recovering.
Jul 2, 16:14 UTC
Jul 2, 16:14 UTC
Investigating -
We are currently investigating this issue.
Jul 2, 16:09 UTC
Jul 2, 16:09 UTC
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
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
We will continue monitoring to ensure stability, but mitigation is complete.
Jul 2, 10:16 UTC
Update -
We are experiencing degraded availability for the Claude Sonnet 4 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.
Jul 2, 09:55 UTC
Jul 2, 09:55 UTC
Investigating -
We are currently investigating this issue.
Jul 2, 09:54 UTC
Jul 2, 09:54 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
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
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
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 30, 19:13 UTC
Resolved -
Due to a degradation of one instance of our internal message delivery service, a percentage of jobs started between 06/30/2025 19:18 UTC and 06/30/2025 19:50 UTC failed, and are no longer retry-able. Runners assigned to these jobs will automatically recover within 24 hours, but deleting and recreating the runner will free up the runner immediately.
Jun 30, 19:00 UTC
Jun 30, 19:00 UTC
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe