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

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

Scheduled Maintenance

Codespaces Scheduled Maintenance May 14, 2025 16:30 - May 15, 2025 16:30 UTC

Codespaces will be undergoing global maintenance from 16:30 UTC on Wednesday, May 14 to 16:30 UTC on Thursday, May 15. 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.
Posted on May 13, 2025 - 19:52 UTC
May 14, 2025

No incidents reported today.

May 13, 2025

No incidents reported.

May 12, 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.
May 12, 15:06 UTC
Investigating - We are currently investigating this issue.
May 12, 14:53 UTC
May 11, 2025

No incidents reported.

May 10, 2025

No incidents reported.

May 9, 2025

No incidents reported.

May 8, 2025
Codespaces Scheduled Maintenance
Completed - The scheduled maintenance has been completed.
May 8, 16:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 7, 16:30 UTC
Scheduled - Codespaces will be undergoing global maintenance from 16:30 UTC on Wednesday, May 7 to 16:30 UTC on Thursday, May 8. 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 6, 19:29 UTC
Incident with Git Operations
Resolved - On May 8, 2025, between 14:40 UTC and 16:27 UTC the Git Operations service was degraded causing some pushes and merges to fail. On average, the error rate was 1.4% with a peak error rate of 2.24%. This was due to a configuration change which unexpectedly led a critical service to shut down on a subset of hosts that store repository data.

We mitigated the incident by re-deploying the affected service to restore its functionality.

In order to prevent similar incidents from happening again, we identified the cause that triggered this behavior and mitigated it for future deployments. Additionally, to reduce time to detection we will improve monitoring of the impacted service.
May 8, 16:27 UTC
Update - Pull Requests is operating normally.
May 8, 16:18 UTC
Update - Actions is operating normally.
May 8, 16:12 UTC
Update - We have identified the issue and applied mitigations, and are monitoring for recovery.
May 8, 16:03 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate.
May 8, 15:23 UTC
Investigating - We are investigating reports of degraded performance for Git Operations and Pull Requests
May 8, 15:20 UTC
May 7, 2025
May 6, 2025

No incidents reported.

May 5, 2025

No incidents reported.

May 4, 2025

No incidents reported.

May 3, 2025

No incidents reported.

May 2, 2025

No incidents reported.

May 1, 2025
Issue Attachments Failing to Upload
Resolved - On May 1, 2025 from 22:09 UTC to 23:13 UTC, the Issues service was degraded and users weren't able to upload attachments. The root cause was identified to be a new feature which added a custom header to all client-side HTTP requests, causing a CORS errors when uploading attachments to our provider.

We mitigated the incident by rolling back the feature flag that added the new header at 22:56 UTC. In order to prevent this from happening again, we are adding new metrics to monitor and ensure the safe rollout of changes to client-side requests.
May 1, 23:13 UTC
Update - We have identified the underlying cause of attachment upload failures to Issues and mitigated it by rolling back a feature flag. If you are still experiencing failures when uploading attachments to Issues, please reload your page.
May 1, 23:13 UTC
Update - We are investigating attachment upload failures on Issues. We will continue to keep users updated on progress towards mitigation.
May 1, 22:29 UTC
Investigating - We are investigating reports of degraded availability for Issues
May 1, 22:28 UTC
Apr 30, 2025
Disruption with Pull Request Ref Updates
Resolved - On April 30, 2025, between 8:02 UTC and 9:05 UTC, the Pull Requests service was degraded and failed to update refs for repositories with higher traffic. This was due to a repository migration creating a larger than usual number of enqueued jobs. This resulted in an increase in job failures, delays for non-migration sourced jobs, and delays to tracking refs.

We declared an incident once we confirmed that this issue was not isolated to the migrating repository and other repositories were also failing to process ref updates.

We mitigated the incident by shifting the migration jobs to a different job queue.

To avoid problems like this in the future, we are revisiting our repository migration process and are working to isolate potentially problematic migration workloads from non-migration workloads.
Apr 30, 21:05 UTC
Update - Some customers of github.com are reporting issues with PR tracking refs not being updated due to processing delays and increased failure rates. We're investigating the source of the issue.
Apr 30, 20:53 UTC
Investigating - We are investigating reports of degraded performance for Pull Requests
Apr 30, 20:51 UTC
← Incident History Powered by Atlassian Statuspage