Skip to content
Back to Microsoft CopilotIncident Postmortem
Microsoft Copilot logo

Microsoft Copilot

Tracked by PulseWatch

Auto-drafted postmortem

Microsoft Copilot outage on May 1 — 51-minute disruption

May 1, 09:06 PM → May 1, 09:57 PM · 51 minutes · high

Microsoft Copilot experienced a service disruption, which was detected through user reports. The incident began on May 1, 2026, at 21:06 UTC and was resolved at 21:57 UTC on the same day.

Peak reports
8
in 15 min
Total reports
11
during the incident
Duration
51 minutes
tracked by PulseWatch

Impact

During the 51-minute disruption, users primarily reported issues categorized as 'AI assistant unavailable' and 'API issues.' A total of 11 reports were received, with a peak of 8 reports within a 15-minute window. The majority of these reports originated from users in the United States, with some reports also coming from the United Kingdom.

Top reported issues

  • AI assistant unavailable8
  • API issues3

Most affected regions

  • United States7
  • United Kingdom1

Incident timeline

  1. May 1, 09:06 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 1, 09:07 PM

    Status updated: major issue

  3. May 1, 09:12 PM

    Status updated: major issue

  4. May 1, 09:15 PM

    Peak of 3 reports in 15 minutes (baseline 1.3)

  5. May 1, 09:57 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 1, 09:06 PM

    Microsoft 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