Part of Microsoft consumer products

Microsoft Copilot Outage History

Microsoft Copilot is up right now

Pingoru has recorded 4 incidents for Microsoft Copilot: 4 in the last 12 months and 0 in the last 90 days.

Source: status.cloud.microsoft

4incidents recorded
4last 12 months
0last 90 days
3 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Microsoft Copilot in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202612 of 720 (0%)
May 202627 of 744 (1%)
June 202614 of 720 (1%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 590 (0%)

Incidents, newest first

Minor June 1, 2026 Users may be unable to access the Microsoft Copilot desktop or web app 3h 40m Microsoft Copilot

Started Jun 01, 2026, 01:55 PM UTC· resolved Jun 01, 2026, 05:35 PM UTC

  1. monitoring Jun 01, 2026, 03:53 PM UTC

    User impact: Users may be unable to access the Microsoft Copilot desktop or web app. Current status: We’re reviewing our telemetry to determine the specific impact and isolate the root cause. Next update by: Monday, June 01, 2026, at 5:00 PM UTC

  2. monitoring Jun 01, 2026, 04:33 PM UTC

    User impact: Users may be unable to access the Copilot desktop or web app. Current status: We're working on getting logs from impacted users to focus our investigative efforts to isolate the source of impact. Start time: Monday, June 01, 2026, at 1:55 PM UTC Next update by: Monday, June 01, 2026, at 5:00 PM UTC

  3. monitoring Jun 01, 2026, 04:46 PM UTC

    User impact: Users may be unable to access the Copilot desktop or web app. Current status: We've received logs from impacted users and are reviewing them to identify the root cause. We're also continuing to monitor our telemetry to determine mitigating actions we can implement in the interim as our investigation progresses. Start time: Monday, June 01, 2026, at 1:55 PM UTC Next update by: Monday, June 01, 2026, at 6:00 PM UTC

  4. monitoring Jun 01, 2026, 05:30 PM UTC

    User impact: Users may be unable to access the Copilot desktop or web app. Current status: We identified a routing issue which is sending Copilot traffic to a portion of infrastructure that is unhealthy, resulting in the access and timeout errors. We're rerouting requests to healthy infrastructure and our telemetry is starting to show service health recovery. Start time: Monday, June 01, 2026, at 1:55 PM UTC Next update by: Monday, June 01, 2026, at 6:00 PM UTC

  5. resolved Jun 01, 2026, 05:55 PM UTC

    User impact: Users may have been unable to access the Copilot desktop or web app. Final status: We've rerouted requests to healthy infrastructure and have confirmed through our telemetry that service health has recovered. Start time: Monday, June 01, 2026, at 1:55 PM UTC End time: Monday, June 01, 2026, at 5:52 PM UTC

Read the full incident report →

Minor May 29, 2026 Users may be unable to use Microsoft Copilot 3h 5m Microsoft Copilot

Started May 29, 2026, 02:30 PM UTC· resolved May 29, 2026, 05:35 PM UTC

  1. monitoring May 29, 2026, 03:50 PM UTC

    User impact: Users may be unable to use Microsoft Copilot. Current status: We're reviewing service telemetry to isolate the source of the issue. Next update by: Friday, May 29, 2026, at 5:30 PM UTC

  2. monitoring May 29, 2026, 05:01 PM UTC

    User impact: Users may be unable to use Microsoft Copilot. Current status: We've identified high utilization on the underlying infrastructure that the Copilot LLM APIs use and are applying mitigations. Additionally, at the Copilot service level, we're reviewing options to change routing paths, throttling rules and retry logic to allow the underlying infrastructure to recover. Next update by: Friday, May 29, 2026, at 6:30 PM UTC

  3. resolved May 29, 2026, 07:01 PM UTC

    User impact: Users were unable to use Microsoft Copilot. Final status: The underlying infrastructure that the Copilot LLM APIs use has recovered after the mitigation actions were applied. We monitored the environment for an extended period of time and have validated that service has been restored. Start time: Friday, May 29, 2026, at 2:30 PM UTC End time: Friday, May 29, 2026, at 5:35 PM UTC This is the final update for this event.

Read the full incident report →

Minor May 14, 2026 Some users may see failures when accessing Microsoft Copilot 3h 44m Microsoft Copilot

Started May 14, 2026, 01:16 PM UTC· resolved May 14, 2026, 05:00 PM UTC

  1. monitoring May 14, 2026, 05:09 PM UTC

    User impact: Users may see failures when accessing Microsoft Copilot More info: Users may be presented with a 401-error response code. Current status: We're investigating a potential issue with Microsoft Copilot and checking for impact to users. We'll provide an update within 30 minutes.

  2. resolved May 14, 2026, 05:43 PM UTC

    User impact: Users may have seen failures when accessing Microsoft Copilot. More info: Users may be presented with a 401-error response code. Final status: We've completed a deployment to roll back to the most recent stable version of the service. Through our service side telemetry, we've confirmed that the service has been restored to a healthy level. Start time: Thursday, May 14, 2026, at 1:16 PM UTC End time: Thursday, May 14, 2026, at 5:00 PM UTC This is the final update for this event.

Read the full incident report →

Minor April 29, 2026 Users may experience issues accessing or using Microsoft Copilot 1h 37m Microsoft Copilot

Started Apr 29, 2026, 01:51 PM UTC· resolved Apr 29, 2026, 03:28 PM UTC

  1. resolved Apr 29, 2026, 04:11 PM UTC

    User impact: Affected users may have been unable to use Copilot services and features. More info: Prompts to Copilot may have returned an error message stating "Oops, Something happened. Can you try again?" Final status: We observed and mitigated an infrastructure issue that caused issues accessing Microsoft Copilot. We redirected traffic to healthy infrastructure and have confirmed that the issue is resolved. Start time: Wednesday, April 29, 2026, at 1:51 PM UTC End time: Wednesday, April 29, 2026, at 3:28 PM UTC This is the final update for the event.

Read the full incident report →