GitHub Status

Feb 27, 2025

Resolved - This incident has been resolved.
Feb 27, 12:22 UTC

Update - The team is confident that recovery is complete. Thank you for your patience as this issue was investigated.
Feb 27, 12:22 UTC

Update - Our mitigations have rolled out successfully and have seen recovery for all Actions run starts back within expected range. Users should see Actions runs working normally.

We will keep this incident open for a short time while we continue to validate these results.
Feb 27, 12:16 UTC

Update - We have identified the cause of the delays to starting Action runs.

Our team is working to roll out mitigations and we hope to see recovery as these take effect in our systems over the next 10-20 minutes.

Further updates as we have more information.
Feb 27, 12:01 UTC

Update - We are seeing an increase in run start delays since 1104 UTC. This is impacting ~3% of Action runs at this time.

The team is working to understand the causes of this and to mitigate impact. We will continue to update as we have more information.
Feb 27, 11:39 UTC

Update - Actions is experiencing degraded performance. We are continuing to investigate.
Feb 27, 11:31 UTC

Investigating - We are currently investigating this issue.
Feb 27, 11:28 UTC

Feb 26, 2025

Incident with Actions and Packages

Resolved - This incident has been resolved.
Feb 26, 17:19 UTC

Update - Actions and Packages are operating normally.
Feb 26, 17:19 UTC

Update - We're continuing our investigation into Billing interfaces and retrieval of packages causing Actions workflow run failures.
Feb 26, 16:41 UTC

Update - We’re investigating issues related to billing and the retrieval of packages that are causing Actions workflow run failures.
Feb 26, 16:17 UTC

Update - We're investigating issues related to the Billing interfaces and Packages downloads failing for enterprise customers.
Feb 26, 15:56 UTC

Investigating - We are investigating reports of degraded performance for Actions and Packages
Feb 26, 15:51 UTC

Feb 25, 2025

Disruption with some GitHub services

Resolved - This incident has been resolved.
Feb 25, 16:50 UTC

Update - Web and email notifications are caught up, resolving the incident.
Feb 25, 16:49 UTC

Update - We're continuing to investigate delayed web and email notifications.
Feb 25, 16:16 UTC

Update - We're continuing to investigate delayed web and email notifications.
Feb 25, 15:43 UTC

Update - We're investigating delays in web and email notifications impacting all customers.
Feb 25, 15:13 UTC

Investigating - We are currently investigating this issue.
Feb 25, 15:12 UTC

Claude 3.7 Sonnet Partially Unavailable

Resolved - This incident has been resolved.
Feb 25, 15:45 UTC

Update - We have disabled Claude 3.7 Sonnet models in Copilot Chat and across IDE integrations (VSCode, Visual Studio, JetBrains) due to an issue with our provider.

Users may still see these models as available for a brief period but we recommend switching to a different model. Other models were not impacted and are available.

Once our provider has resolved the issues impacting Claude 3.7 Sonnet models, we will re-enable them.
Feb 25, 15:25 UTC

Update - Copilot is experiencing degraded performance. We are continuing to investigate.
Feb 25, 14:44 UTC

Update - We are currently experiencing partial availability for the Claude 3.7 Sonnet and Claude 3.7 Thinking models in Copilot Chat, VSCode and other Copilot products. This is due to problems with an upstream provider. We are working to resolve these issues and will update with more information as it is made available.

Other Copilot models are available and working as expected.
Feb 25, 14:43 UTC

Investigating - We are currently investigating this issue.
Feb 25, 14:40 UTC

Incident with Packages

Resolved - This incident has been resolved.
Feb 25, 01:08 UTC

Update - We have confirmed recovery for the majority of our systems. Some systems may still experience higher than normal latency as they catch up.
Feb 25, 01:08 UTC

Update - We have identified the issue impacting packages and have rolled out a fix. We are seeing signs of recovery and continue to monitor the situation.
Feb 25, 00:41 UTC

Investigating - We are investigating reports of degraded performance for Packages
Feb 25, 00:17 UTC

Feb 24, 2025

Claude 3.5 Sonnet model is unavailable in Copilot

Resolved - This incident has been resolved.
Feb 24, 22:14 UTC

Update - We were able to quickly identify the problem and resolve this issue. Claude 3.5 Sonnet is available again.
Feb 24, 22:14 UTC

Update - At this time, we are unable to serve requests to the Claude 3.5 Sonnet on Copilot. No other models are affected. We are investigating the issue and will provide updates as we discovery more information.
Feb 24, 22:08 UTC

Investigating - We are investigating reports of degraded performance for Copilot
Feb 24, 22:06 UTC

Disruption with some GitHub services

Resolved - This incident has been resolved.
Feb 24, 18:31 UTC

Update - We have restored all of the data for 2025-02-21 to 2025-02-23. The data is queryable through the Copilot Metrics API. We are continuing to monitor the metrics data and expect to resolve the incident in the next hour.
Feb 24, 18:25 UTC

Update - We expect the missing data from the weekend to be available within two hours.
Feb 24, 17:50 UTC

Update - Copilot-metrics is in the process of restoring the usage statistics for 2025-02-23, we will continue to restore the previous 2 days over the next few hours.
Feb 24, 16:28 UTC

Update - Customers may not be able to review their usage statistics for copilot starting Saturday through Monday morning UTC. The API is functioning normally, but no data is available for those time periods. We are working on backfilling the data and all metrics will be eventually available later today. We estimate recovery within in the next few hours and will provide updates on this as the recovery process proceeds.
Feb 24, 15:56 UTC

Update - We are investigating reports of issues with service: Copilot metrics API. We will continue to keep users updated on progress towards mitigation.
Feb 24, 15:19 UTC

Investigating - We are currently investigating this issue.
Feb 24, 15:17 UTC

Incident with Issues

Resolved - This incident has been resolved.
Feb 24, 17:09 UTC

Update - Pull Requests is operating normally.
Feb 24, 17:09 UTC

Update - Issues is operating normally.
Feb 24, 17:09 UTC

Update - We continue to see recovery and expect Pull Requests and Issues search queries to recover within 30 minutes.
Feb 24, 16:48 UTC

Update - We are seeing recovery and expect for Pull Requests and Issues search queries to recover within 15 minutes.
Feb 24, 16:29 UTC

Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.
Feb 24, 16:14 UTC

Investigating - We are investigating reports of degraded performance for Issues
Feb 24, 16:08 UTC

Feb 23, 2025

No incidents reported.

Feb 22, 2025

No incidents reported.

Feb 21, 2025

No incidents reported.

Feb 20, 2025

No incidents reported.

Feb 19, 2025

No incidents reported.

Feb 18, 2025

No incidents reported.

Feb 17, 2025

No incidents reported.

Feb 16, 2025

Disruption with some GitHub services

Resolved - This incident has been resolved.
Feb 16, 12:44 UTC

Update - Pull Requests is operating normally.
Feb 16, 12:43 UTC

Update - Webhooks is operating normally.
Feb 16, 12:43 UTC

Update - API Requests is operating normally.
Feb 16, 12:43 UTC

Update - Issues is operating normally.
Feb 16, 12:42 UTC

Update - Codespaces is operating normally.
Feb 16, 12:42 UTC

Update - Git Operations is operating normally.
Feb 16, 12:42 UTC

Update - Actions is operating normally.
Feb 16, 12:42 UTC

Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.
Feb 16, 12:24 UTC

Update - API Requests is experiencing degraded performance. We are continuing to investigate.
Feb 16, 12:10 UTC

Investigating - We are investigating reports of degraded performance for Actions, Codespaces, Git Operations, Issues and Webhooks
Feb 16, 12:08 UTC

Feb 15, 2025

Disruption with some GitHub services

Resolved - This incident has been resolved.
Feb 15, 04:15 UTC

Update - We completed the rollout. GitHub Codespaces are healthy.
Feb 15, 04:15 UTC

Update - We continue the rollout in Central India, SE Asia, and Australia Codespaces regions. We are seeing a minimal number of connection failures across all regions at the moment.
Feb 15, 03:21 UTC

Update - We rolled out a fix to most of our Codespaces regions. Central India, SE Asia, and Australia are the remaining regions to be fixed. Customers in these remaining regions can be experiencing issues with Codespaces connectivity.
Feb 15, 01:47 UTC

Update - Some customers are continuing to see intermittent connection failures to their codespaces. We are monitoring closely to build a better idea of when impact should be mitigated. At this time, we expect the number of impacted users to remain low, and will update again when there is a development in our repair efforts.
Feb 14, 20:53 UTC

Update - Codespaces is experiencing degraded performance. We are continuing to investigate.
Feb 14, 20:22 UTC

Update - Some GitHub codespace users are experiencing intermittent connection failures. A deployment is underway to mitigate the problem, and US-based customers should see recovery soon. Full recovery is expected to take several hours. In the meantime, we advise customers experiencing issues to retry their connection attempts.
Feb 14, 20:12 UTC

Investigating - We are currently investigating this issue.
Feb 14, 20:06 UTC

Feb 14, 2025

Feb 13, 2025

[Retroactive] Incident with Migrations service

Resolved - Between Thursday 13th, 2025 19:30 UTC and Friday 14th, 2025 08:02 UTC the Migrations service was experiencing intermittent migration failures for some customers. This was caused by a code change that contained an edge case that erroneously failed some migrations.

We mitigated the incident by rolling back the code change.

We are working on improving our monitoring and deployment practices to reduce our time to detection and mitigation of issues like this one in the future.
Feb 13, 07:30 UTC

About This Site