GitHub header

Disruption with some GitHub services

Incident Report for GitHub

Resolved

On February 15, 2025, between 6:35 pm UTC and 4:15 am UTC the Codespaces service was degraded and users in various regions experienced intermittent connection failures. On average, the error rate was 50% and peaked at 65% of requests to the service. This was due to a service deployment.

We mitigated the incident by completing the deployment to the impacted regions.

The completion of this deployment should prevent future deployments of the service from negatively impacting Codespace connectivity.
Posted Feb 15, 2025 - 04:15 UTC

Update

We completed the rollout. GitHub Codespaces are healthy.
Posted Feb 15, 2025 - 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.
Posted Feb 15, 2025 - 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.
Posted Feb 15, 2025 - 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.
Posted Feb 14, 2025 - 20:53 UTC

Update

Codespaces is experiencing degraded performance. We are continuing to investigate.
Posted Feb 14, 2025 - 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.
Posted Feb 14, 2025 - 20:12 UTC

Investigating

We are currently investigating this issue.
Posted Feb 14, 2025 - 20:06 UTC
This incident affected: Codespaces.