Skip to content
Back to GitHub CopilotIncident Postmortem
GitHub Copilot logo

GitHub Copilot

Tracked by PulseWatch

Auto-drafted postmortem

GitHub Copilot outage on May 5 — 5h 24m disruption

May 5, 01:39 PM → May 5, 07:03 PM · 5h 24m · medium

On May 5, 2026, GitHub Copilot experienced an outage that was detected through user reports. The incident began at approximately 13:39 UTC and was fully resolved by 19:03 UTC, resulting in a disruption lasting 5 hours and 24 minutes.

Peak reports
10
in 15 min
Total reports
84
during the incident
Duration
5h 24m
tracked by PulseWatch

Impact

During the incident, users primarily reported issues related to GitHub Copilot being slow or unresponsive. A total of 84 user reports were received, with a peak of 10 reports within a 15-minute period. While the majority of reports indicated performance issues, a small number also cited security concerns. No specific regional impact was recorded for this event.

Top reported issues

  • Slow / unresponsive80
  • Security issue4

Incident timeline

  1. May 5, 01:39 PM

    PulseWatch detected elevated report volume (medium severity)

  2. May 5, 01:43 PM

    Status updated: possible issue

  3. May 5, 01:53 PM

    Status updated: possible issue

  4. May 5, 01:58 PM

    Status updated: possible issue

  5. May 5, 02:08 PM

    Status updated: possible issue

  6. May 5, 02:13 PM

    Status updated: possible issue

  7. May 5, 02:23 PM

    Status updated: possible issue

  8. May 5, 02:28 PM

    Status updated: possible issue

  9. May 5, 02:38 PM

    Status updated: possible issue

  10. May 5, 02:43 PM

    Status updated: possible issue

  11. May 5, 02:53 PM

    Status updated: possible issue

  12. May 5, 02:58 PM

    Status updated: possible issue

  13. May 5, 03:08 PM

    Status updated: possible issue

  14. May 5, 03:13 PM

    Status updated: possible issue

  15. May 5, 03:23 PM

    Status updated: possible issue

  16. May 5, 03:28 PM

    Status updated: possible issue

  17. May 5, 03:38 PM

    Status updated: possible issue

  18. May 5, 05:15 PM

    Peak of 8 reports in 15 minutes (baseline 1.3)

  19. May 5, 07:03 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 5, 01:39 PM

    GitHub Copilot status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals and the sources listed above.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash