Investigating errors on GitHub

What to do

• Check whether you use GitHub Copilot Actions, Packages, Copilot, Codespaces. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 38m it lasted.

  Anything that failed between 2026-04-23 14:40 UTC and 2026-04-23 15:18 UTC may need a replay.

• Subscribe to GitHub Copilot's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github-copilot works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub Copilot 8

1. investigatingApr 23, 2026, 2:40 PM UTC

   We are investigating reports of degraded performance for Actions

   provider

2. investigatingApr 23, 2026, 2:41 PM UTC

   Packages is experiencing degraded performance. We are continuing to investigate.

   provider

3. investigatingApr 23, 2026, 2:42 PM UTC

   Codespaces is experiencing degraded performance. We are continuing to investigate.

   provider

4. investigatingApr 23, 2026, 2:44 PM UTC

   Copilot is experiencing degraded performance. We are continuing to investigate.

   provider

5. investigatingApr 23, 2026, 2:51 PM UTC

   Users are experiencing errors loading various web pages on github.com. Actions and Copilot Cloud Agent runs will be delayed.

   provider

6. investigatingApr 23, 2026, 3:02 PM UTC

   A mitigation was applied and services have recovered.  Actions is working through queued work before fully recovering.

   provider

7. monitoringApr 23, 2026, 3:02 PM UTC

   The degradation affecting Actions, Codespaces, Copilot and Packages has been mitigated. We are monitoring to ensure stability.

   provider

8. resolvedApr 23, 2026, 3:18 PM UTC

   On April 23, 2026 between 14:30 UTC and 15:18 UTC multiple services were degraded on github.com. During this time approximately 1.5% of all web requests resulted in a 5xx status and unicorn pages for github.com users. We also saw elevated error rates across Actions workflow runs, Copilot, Codespaces and Packages, leading to degraded experiences during this timeframe. Codespaces impact peaked at 45% failures for create requests and 65% failures for resume requests. Packages impact was mainly Maven related with 50% failure rates in downloads and 70% failure rates in uploads. Actions experienced a peak of 8% of failed jobs and up to 85% of jobs impacted by run start delays of more than 5 minutes. This was due to a configuration change to an internal billing service that led to a cache being overwhelmed and causing requests to time out. These timeouts cascaded across multiple services and eventually caused requests to queue up and exhaust web request workers. This configuration change was reverted at 14:42 UTC and following this, all services began to see recovery immediately. To prevent this situation in the future, we are taking steps to ensure that failures and timeouts in the billing service don’t cascade to other services causing impact. This includes implementing more aggressive timeouts on callers of these billing services, adding circuit breaker configurations for cache timeouts and using more resilient cache options. We have also decreased max request timeouts within the billing service that caused impact and added more capacity to our cache to prevent traffic spikes from having the same impact.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.