Critical impactResolvedDevOps

GitHub outage: Intermittent failures creating agent tasks

GitHub reported this critical-impact incident on its official status page on Aug 20, 2026, 14:43 UTC. It was resolved after 9h 54m.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
Aug 20, 2026, 14:43 UTC
started
Aug 21, 2026, 00:37 UTC
resolved
9h 54m
duration
Critical
impact
  1. resolvedAug 21, 2026, 00:37 UTC

    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.<br /><br />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.<br /><br />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.

  2. investigatingAug 20, 2026, 20:37 UTC

    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.

  3. investigatingAug 20, 2026, 19:35 UTC

    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.

  4. investigatingAug 20, 2026, 18:45 UTC

    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.

  5. investigatingAug 20, 2026, 18:04 UTC

    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.

  6. investigatingAug 20, 2026, 17:32 UTC

    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.

  7. investigatingAug 20, 2026, 17:05 UTC

    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.

  8. investigatingAug 20, 2026, 16:14 UTC

    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.

  9. investigatingAug 20, 2026, 15:41 UTC

    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.

  10. investigatingAug 20, 2026, 15:01 UTC

    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.

  11. investigatingAug 20, 2026, 14:51 UTC

    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.

  12. investigatingAug 20, 2026, 14:43 UTC

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

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitHub's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does GitHub have incidents?

GitHub reported 49 incidents in the last 90 days, 15 of them major or critical. A typical incident lasted 1h 16m. See GitHub's uptime and incident history