Skip to main content
GitHub

Incident with Codespaces

Degraded Lasted 48m · started · GitHub's page

Level
confirmed
Worst impact
Degraded
Components
Codespaces
Regions
au
Down Index
21of 100

What to do

  • Check whether you use GitHub Codespaces in au. 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 48m it lasted.

    Anything that failed between 2026-03-09 03:04 UTC and 2026-03-09 03:51 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 5

  1. investigating

    We are investigating reports of degraded performance for Codespaces

    provider

  2. investigating

    We are seeing about 5% of new Codespace creation requests failing. We are investigating the root cause and identifying the impacted regions.

    provider

  3. investigating

    We are seeing recovery, with the failure rate for new Codespace creation requests dropping from 5% to about 3%.

    provider

  4. investigating

    This incident has been resolved. New Codespace creation requests are now completing successfully.

    provider

  5. resolved

    On March 9, 2026, between 01:23 UTC and 03:25 UTC, users attempting to create or resume codespaces in the Australia East region experienced elevated failures, peaking at a 100% failure rate for this region. Codespaces in other regions were not affected. The create and resume failures were caused by degraded network connectivity between our control plane services and the VMs hosting the codespaces. This was resolved by redirecting traffic to an alternate site within the region. While we are addressing the core network infrastructure issue, we have also improved our observability of components in this area to improve detection. This will also enable our existing automated failovers to cover this failure mode. These changes will prevent or significantly reduce the time any similar incident causes user impact.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-1a4063f7fe

Is GitHub still down?

No, this incident was resolved 2026-03-09 03:51 UTC. For GitHub's live state, see https://down.guide/github.

How long did it last?

48m, from 2026-03-09 03:04 UTC to 2026-03-09 03:51 UTC, by the times GitHub posted.

What was affected?

GitHub named Codespaces in au.

What caused it?

GitHub hasn't published a root cause. If it does, it shows here.

Where does this come from?

GitHub's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.