- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 15of 100
What to do
Check whether your product depends on GitHub. 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 24m it lasted.
Anything that failed between 2026-10-15 18:31 UTC and 2026-10-15 18: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
- investigating
We are investigating reports of impacted performance for some GitHub services.
provider
- investigating
CCA Automations are experiencing delays when users start an Automation
provider
- monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
provider
- resolved
We suspected that CCA Automations were experiencing delays when users start an Automation, but further investigation found that there was no delay or impact to CCA Automations.
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-d486170178
Is GitHub still down?
No, this incident was resolved 2026-10-15 18:56 UTC. For GitHub's live state, see https://down.guide/github.
How long did it last?
24m, from 2026-10-15 18:31 UTC to 2026-10-15 18:56 UTC, by the times GitHub posted.
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.