Skip to main content
GitHub

Degraded experience with Copilot Code Review

Degraded Lasted 1h 28m · started · GitHub's page

Level
confirmed
Worst impact
Degraded
Down Index
18of 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 1h 28m it lasted.

    Anything that failed between 2026-03-11 14:25 UTC and 2026-03-11 15:53 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 impacted performance for some GitHub services.

    provider

  2. monitoring

    We are investigating degraded performance with Copilot Code Review. Customers may experience extended review times or occasional failures. We are seeing signs of improvement as our team works to restore normal service. We'll post another update by 15:30 UTC.

    provider

  3. monitoring

    We experienced degraded performance with Copilot Code Review starting at 14:01 UTC. Customers experienced extended review times and occasional failures. Some extended processing times may continue briefly. We are monitoring for full recovery. We'll post another update by 16:30 UTC.

    provider

  4. monitoring

    Copilot Code Review queue processing has returned to normal levels.

    provider

  5. resolved

    On March 11, 2026, between 13:00 UTC and 15:23 UTC the Copilot Code Review service was degraded and experienced longer than average review times. On average, Copilot Code Review requests took 4 minutes and peaked at just under 8 minutes. This was due to hitting worker capacity limits and CPU throttling. We mitigated the incident by increasing partitions, and we are improving our resource monitoring to identify potential issues sooner.

    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-70f52ffdc8

Is GitHub still down?

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

How long did it last?

1h 28m, from 2026-03-11 14:25 UTC to 2026-03-11 15:53 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.