EU - Issues with Copilot Coding Agent

Update timeline

1. investigating Mar 19, 2026, 10:41 AM UTC

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

2. investigating Mar 19, 2026, 10:43 AM UTC

   We are investigating reports of errors when accessing Copilot Coding Agent features. Users may be unable to view or start coding agent tasks through the Agents interface. Our engineers are actively working to restore full functionality.

3. investigating Mar 19, 2026, 11:19 AM UTC

   We believe we have identified an underlying credential issue and are working to resolve that across impacted environments.

4. investigating Mar 19, 2026, 12:00 PM UTC

   We have resolved the underlying credential issue and have verified that users can see and interact with their Copilot Coding Agent tasks. We are now investigating issues with some Coding Agent tasks completing successfully.

5. investigating Mar 19, 2026, 12:32 PM UTC

   We are investigating reports of Copilot coding agent session logs not loading and sessions intermittently not starting. Users are able to see their tasks and create new ones.

6. investigating Mar 19, 2026, 01:45 PM UTC

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

7. investigating Mar 19, 2026, 02:02 PM UTC

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

8. monitoring Mar 19, 2026, 02:32 PM UTC

   Copilot is operating normally.

9. resolved Mar 19, 2026, 02:32 PM UTC

   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.