Skip to main content
GitHub Copilot

Issues with Copilot Coding Agent

Partial outage Lasted 49m · started · GitHub Copilot's page

Level
confirmed
Worst impact
Partial outage
Components
Copilot
Down Index
37of 100

What to do

  • Check whether you use GitHub Copilot Copilot. 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 49m it lasted.

    Anything that failed between 2026-03-19 13:44 UTC and 2026-03-19 14:32 UTC may need a replay.
  • Subscribe to GitHub Copilot's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=github-copilot works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub Copilot 5

  1. investigating

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

    provider

  2. investigating

    Copilot is experiencing degraded performance. We are continuing to investigate.

    provider

  3. investigating

    We are investigating reports that Copilot Coding Agent session logs are not available in the UI.

    provider

  4. investigating

    Copilot is operating normally.

    provider

  5. resolved

    On March 19, 2026, between 01:05 UTC and 02:52 UTC, and again on March 20, 2026, between 00:42 UTC and 01:58 UTC, the Copilot Coding Agent service was degraded and users were unable to start new Copilot Agent sessions or view existing ones. During the first incident, the average error rate was ~53% and peaked at ~93% of requests to the service. During the second incident, the average error rate was ~99%% and peaked at ~100%% of requests with significant retry amplification. Both incidents were caused by the same underlying system authentication issue that prevented the service from connecting to its backing datastore. We mitigated each incident by rotating the affected credentials, which restored connectivity and returned error rates to normal. The mitigation time was 01:24. The second occurrence was due to an incomplete remediation of the first. We are implementing automated monitoring for credential lifecycle events and improving operational processes to reduce our time to detection and mitigation of issues like this one in the future.

    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-0971a0759c

Is GitHub Copilot still down?

No, this incident was resolved 2026-03-19 14:32 UTC. For GitHub Copilot's live state, see https://down.guide/github-copilot.

How long did it last?

49m, from 2026-03-19 13:44 UTC to 2026-03-19 14:32 UTC, by the times GitHub Copilot posted.

What was affected?

GitHub Copilot named Copilot.

What caused it?

GitHub Copilot hasn't published a root cause. If it does, it shows here.

Where does this come from?

GitHub Copilot's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.