The Wayback Machine - https://web.archive.org/web/20250612053416/https://www.githubstatus.com/
GitHub header

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
Jun 12, 2025

No incidents reported today.

Jun 11, 2025
Disruption with some GitHub services
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.
Jun 11, 01:51 UTC
Update - Fix is currently rolling out to production. We will update here once we verify.
Jun 11, 01:08 UTC
Update - We are working to deploy the fix for this issue. We will update again once it is deployed and as we monitor recovery.
Jun 10, 23:32 UTC
Update - We have the fix ready, once it's ready to deploy we will provide another update confirming that it has resolved the issue.
Jun 10, 22:42 UTC
Update - We have identified the solution to the performance issue and are working on the mitigation. Impact continues to be limited to very large enterprise customers when viewing the People page.
Jun 10, 21:04 UTC
Update - The mitigation to add a supporting index to improve the performance of the People page did not resolve the issue, and we are continuing to investigate a solution.
Jun 10, 20:09 UTC
Update - We are working on the mitigation and anticpate recovery within an hour.
Jun 10, 18:57 UTC
Update - Large enterprise customers may encounter issues loading the People page
Jun 10, 18:35 UTC
Investigating - We are currently investigating this issue.
Jun 10, 18:17 UTC
Jun 10, 2025
Codespaces billing is delayed
Resolved - This incident has been resolved.
Jun 10, 19:08 UTC
Update - We've increased capacity to process the codespaces billing jobs and see are seeing recovery, we expect a full mitigation within the hour.
Jun 10, 18:21 UTC
Investigating - We are currently investigating this issue.
Jun 10, 17:47 UTC
Incident with Pull Requests
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.
Jun 10, 14:46 UTC
Investigating - We are investigating reports of degraded performance for Pull Requests
Jun 10, 14:28 UTC
Jun 9, 2025

No incidents reported.

Jun 8, 2025

No incidents reported.

Jun 7, 2025

No incidents reported.

Jun 6, 2025
Incident With Copilot
Resolved - On June 6, 2025, an update to mitigate a previous incident led to automated scaling of database infrastructure used by Copilot Coding Agent. The clients of the service were not implemented to automatically handle an extra partition. Hence it was unable to retrieve data across partitions, resulting in unexpected 404 errors.

As a result, approximately 17% of coding sessions displayed an incorrect final state - such as sessions appearing in-progress when they were actually completed. Additionally, some Copilot-authored pull requests were missing timeline events indicating task completion. Importantly, this did not affect Copilot Coding Agent’s ability to finish code tasks and submit pull requests.

To prevent similar issues in the future we are taking steps to improve our systems and monitoring.
Jun 6, 23:00 UTC
Incident with Copilot
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.
Jun 6, 12:40 UTC
Update - Copilot is operating normally.
Jun 6, 12:40 UTC
Update - We are continuing to monitor recovery and expect a complete resolution very shortly.
Jun 6, 12:18 UTC
Update - The changes have been reverted and we are seeing signs of recovery. We expect impact to be largely mitigated, but are continuing to monitor and will update further as progress continues.
Jun 6, 11:31 UTC
Update - We have identified changes that may be causing the issue and are working to revert the offending changes. We will continue to keep users updated as we work toward mitigation.
Jun 6, 10:39 UTC
Update - We are investigating reports of users unable to utilize Copilot Free after a trial subscription has ended for Copilot Pro. We will continue to keep users updated on progress towards mitigation.
Jun 6, 10:04 UTC
Investigating - We are investigating reports of degraded performance for Copilot
Jun 6, 09:58 UTC
Jun 5, 2025
Incident with Actions
Resolved - On June 5th, 2025, between 17:47 UTC and 19:20 UTC the Actions service was degraded, leading to run start delays and intermittent job failures. During this period, 47.2% of runs had delayed starts, and 21.0% of runs failed. The impact extended beyond Actions itself - 60% of Copilot Coding Agent sessions were cancelled, and all Pages sites using branch-based builds failed to deploy (though Pages serving remained unaffected). The issue was caused by a spike in load between internal Actions services exposing a misconfiguration that caused throttling of requests in the critical path of run starts. We mitigated the incident by correcting the service configuration to prevent throttling and have updated our deployment process to ensure the correct configuration is preserved moving forward.
Jun 5, 19:29 UTC
Update - We have applied a mitigation and we are beginning to see recovery. We are continuing to monitor for recovery.
Jun 5, 19:02 UTC
Update - Actions is experiencing degraded availability. We are continuing to investigate.
Jun 5, 18:35 UTC
Update - Users of Actions will see delays in jobs starting or job failures. Users of Pages will see slow or failed deployments
Jun 5, 18:30 UTC
Update - Pages is experiencing degraded performance. We are continuing to investigate.
Jun 5, 18:01 UTC
Investigating - We are investigating reports of degraded performance for Actions
Jun 5, 18:00 UTC
Jun 4, 2025
Incident with Actions
Resolved - On June 4, 2025, between 14:35 UTC and 15:50 UTC , the Actions service experienced degradation, leading to run start delays. During the incident, about 15.4% of all workflow runs were delayed by an average of 16 minutes. An unexpected load pattern revealed a scaling issue in our backend infrastructure. We mitigated the incident by blocking the requests that triggered this pattern.

We are improving our rate limiting mechanisms to better handle unexpected load patterns while maintaining service availability. We are also strengthening our incident response procedures to reduce the time to mitigate for similar issues in the future.
Jun 4, 15:55 UTC
Update - We have applied mitigations and are monitoring for recovery.
Jun 4, 15:39 UTC
Update - We are currently investigating delays with Actions triggering for some users.
Jun 4, 15:19 UTC
Investigating - We are investigating reports of degraded performance for Actions
Jun 4, 15:15 UTC
Jun 3, 2025

No incidents reported.

Jun 2, 2025

No incidents reported.

Jun 1, 2025

No incidents reported.

May 31, 2025
Codespaces Scheduled Maintenance
Completed - The scheduled maintenance has been completed.
May 31, 04:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 29, 21:30 UTC
Scheduled - Codespaces will be undergoing global maintenance from May 29, 2025 21:30 UTC to May 31, 2025 4:30 UTC. Maintenance will begin in our Europe, Asia, and Australia regions. Once it is complete, maintenance will start in our US regions. Each batch of regions will take approximately three to four hours to complete.

During this time period, users may experience intermittent connectivity issues when creating new Codespaces or accessing existing ones.

To avoid disruptions, ensure that any uncommitted changes are committed and pushed before the maintenance starts. Codespaces with uncommitted changes will remain accessible as usual after the maintenance is complete.
May 29, 21:01 UTC
May 30, 2025
Disruption with some GitHub services
Resolved - On May 30, 2025, between 08:10 UTC and 16:00 UTC, the Microsoft Teams GitHub integration service experienced a complete service outage.

During this period, the service was unable to deliver notifications or process user requests, resulting in a 100% error rate for all integration functionality except link previews.

This outage was due to an authentication issue with our downstream provider. We mitigated the incident by working with our provider to restore service functionality and are working to migrate to more durable authentication methods to reduce the risk of similar issues in the future.
May 30, 15:57 UTC
Update - Our team is continuing to work to mitigate the source of the disruption affecting a small set of customers using the GitHub Microsoft Teams integration.
May 30, 14:47 UTC
Update - We are experiencing a disruption with our Microsoft Teams integration. Investigations are underway and we will provide further updates as we progress.
May 30, 12:29 UTC
Investigating - We are currently investigating this issue.
May 30, 11:20 UTC
May 29, 2025
Codespaces Scheduled Maintenance
Completed - The scheduled maintenance has been completed.
May 29, 16:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 28, 16:30 UTC
Scheduled - Codespaces will be undergoing global maintenance from 16:30 UTC on Wednesday, May 28 to 16:30 UTC on Thursday, May 29. Maintenance will begin in our Europe, Asia, and Australia regions. Once it is complete, maintenance will start in our US regions. Each batch of regions will take approximately three to four hours to complete.

During this time period, users may experience intermittent connectivity issues when creating new Codespaces or accessing existing ones.

To avoid disruptions, ensure that any uncommitted changes are committed and pushed before the maintenance starts. Codespaces with uncommitted changes will remain accessible as usual after the maintenance is complete.
May 22, 15:26 UTC
← Incident History Powered by Atlassian Statuspage