Disruption with some GitHub services

What to do

• Check whether you use GitHub 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 1h 35m it lasted.

  Anything that failed between 2026-07-14 08:21 UTC and 2026-07-14 09:56 UTC may need a replay.

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

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

Updates from GitHub 4

1. investigatingJul 14, 2026, 8:21 AM UTC

   We are investigating reports of impacted performance for some GitHub services.

   provider

2. investigatingJul 14, 2026, 8:22 AM UTC

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

   provider

3. monitoringJul 14, 2026, 9:51 AM UTC

   The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.

   provider

4. resolvedJul 14, 2026, 9:56 AM UTC

   On July 14, 2026, the GitHub Codespaces service was degraded during two periods — between 06:00 UTC and 09:56 UTC, and again between 10:54 UTC and 12:53 UTC — and some users experienced intermittent failures or delays when creating new codespaces. Impact was concentrated in a subset of geographic regions. During the first period, the error rate averaged 0.5% and peaked at 4.6% of codespace creation requests. The second period was more pronounced, peaking at approximately 30% of codespace creation requests in the most-affected region before recovery. Both periods were caused by an unexpected surge in codespace creation from an abusive actor that drained the available compute capacity in the affected regions faster than it could be replenished. We mitigated the impact by identifying and stopping the sources of the excess creation volume, reducing the resources that could be consumed in the affected regions, and rebalancing traffic across regions to restore capacity. Codespace creation success rates returned to normal after each period. We are working to add automated, low-latency controls to throttle abnormal codespace creation and to strengthen our detection and safeguards, so we can reduce our time to detection and mitigation of issues like this in the future.

   provider

Corrections

None so far.

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