GitHub Status

Issues with Copilot Coding Agent

Resolvedmajor impactVendor link

Started

Mar 19, 1:44 PM

Resolved

Mar 19, 2:32 PM

Duration

48m

Affected Components

Copilot

Update Timeline

ResolvedMar 19, 2:32 PM

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

InvestigatingMar 19, 2:06 PM

Copilot is operating normally.

InvestigatingMar 19, 2:02 PM

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

InvestigatingMar 19, 1:45 PM

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

InvestigatingMar 19, 1:44 PM

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

Issues with Copilot Coding Agent — GitHub Incident | DevHelm