- 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 17m it lasted.
Anything that failed between 2026-03-05 01:13 UTC and 2026-03-05 01:30 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
Users were temporarily unable to see tasks listed in mission control surfaces. The ability to submit new tasks, view existing tasks via direct link, or manage tasks was unaffected throughout. A revert is currently being deployed and we are seeing recovery.
provider
- investigating
Copilot coding agent mission control is fully restored. Tasks are now listed as expected.
provider
- resolved
On March 5, 2026, between 12:53 UTC and 13:35 UTC, the Copilot mission control service was degraded. This resulted in empty responses returned for users' agent session lists across GitHub web surfaces. Impacted users were unable to see their lists of current and previous agent sessions in GitHub web surfaces. This was caused by an incorrect database query that falsely excluded records that have an absent field. We mitigated the incident by rolling back the database query change. There were no data alterations nor deletions during the incident. To prevent similar issues in the future, we're improving our monitoring depth to more easily detect degradation before changes are fully rolled out.
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-1abba918ac
Is GitHub still down?
No, this incident was resolved 2026-03-05 01:30 UTC. For GitHub's live state, see https://down.guide/github.
How long did it last?
17m, from 2026-03-05 01:13 UTC to 2026-03-05 01:30 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.