- Level
- confirmed
- Worst impact
- Major outage
- Regions
- us
- Down Index
- 49of 100
What to do
Check whether you use GitHub in us. 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 9h 54m it lasted.
Anything that failed between 2026-08-20 14:43 UTC and 2026-08-21 00:37 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 12
- investigating
We are investigating reports of impacted performance for some GitHub services.
provider
- investigating
Users may experience delays when starting tasks using Copilot Cloud Agent. We are actively investigating the issue and will provide updates as we learn more.
provider
- investigating
We have identified the problematic component and are working to fail over to a healthy instance. Further updates will be provided as we perform mitigations.
provider
- investigating
We are experiencing issues with Copilot Cloud Agent tasks, resulting in newly started tasks not properly displaying on-going progress. These Copilot Cloud Agent tasks are still being completed correctly but lack proper visibility. We are actively investigating the issue and will provide updates as we learn more.
provider
- investigating
Users are experiencing delays when starting tasks using Copilot Cloud Agent and are not be able to see the status of these tasks. Copilot Cloud Agent tasks are still being completed. We have identified the cause of the issue and are putting mitigations in place to return service to normal levels. We will provide another update about the expected recovery time shortly.
provider
- investigating
We are seeing signs of recovery for Copilot Cloud Agent task status visibility, but this recovery is slower than anticipated. We are pursuing additional mitigating measures to accelerate recovery.
provider
- investigating
We are observing gradual recovery for Copilot Cloud Agent task status visibility, with session output delayed approximately 1 hour. We have taken additional steps to accelerate the recovery and are continuing to monitor the impact.
provider
- investigating
We are continuing to observe gradual recovery for Copilot Cloud Agent task status visibility, with session output delayed by approximately 1 hour. We have taken additional steps to accelerate the recovery and are continuing to monitor the impact.
provider
- investigating
We are continuing to observe gradual recovery for Copilot Cloud Agent task status visibility, with session output delayed by approximately 1 hour. We have taken additional steps to accelerate the recovery and expect this to take effect within the next hour.
provider
- investigating
We are continuing to observe gradual recovery for Copilot Cloud Agent task status visibility. Session output continues to be delayed by approximately 1 hour as our remediation steps take effect.
provider
- investigating
We are seeing gradual recovery in Copilot Cloud Agent task status visibility as we deploy a fix for the root cause. Session output remains delayed by approximately one hour while remediation continues.
provider
- resolved
Between 13:57 UTC on August 20 and 00:37 UTC on August 21, 2026, some users of the Copilot Cloud Agent experienced delays of up to 60 to 90 minutes in seeing the status and results of their agent tasks. The agent tasks themselves continued to run and complete during this time; only the visibility of their status was delayed. The cause was a regional outage in a third-party cloud database service that Copilot uses to store agent task status. We failed over the affected database to a healthy region, added processing capacity to work through the backlog, and restored normal operation once the underlying service recovered. No task data was lost during the incident. To prevent repetition of similar incidents, we are removing the database configuration that made us vulnerable to this regional outage and improving our database failover procedures.
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-0ca901ec02
Is GitHub still down?
No, this incident was resolved 2026-08-21 00:37 UTC. For GitHub's live state, see https://down.guide/github.
How long did it last?
9h 54m, from 2026-08-20 14:43 UTC to 2026-08-21 00:37 UTC, by the times GitHub posted.
What was affected?
GitHub named in us.
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.