# Microsoft Copilot status

> Is Microsoft Copilot down? Live status, uptime history, and per-region response times measured by our own probes every 2 minutes.

Published: 2026-09-08 | Canonical: https://yoping.me/status/copilot

## How we check Microsoft Copilot

We watch copilot.microsoft.com from all five of our probe regions, every 2 minutes. A region that sees a failure does not make this page say "down" on its own: a second region has to agree first, the same confirmation rule every YoPingMe monitor uses.

We watch Copilot's own web host and pin the response an anonymous request receives, rather than assuming a 2xx. Copilot is embedded across Windows, Microsoft 365, and Edge as well as offered standalone, so a reading of the dedicated web app is the clearest single signal available without claiming to cover every surface it appears on.

The live board - the current verdict, 24-hour, 7-day, and 30-day uptime, and per-region response times - is on the HTML page at https://yoping.me/status/copilot. Those numbers change too fast to repeat honestly in a static mirror, so where an answer below says "the board above", it means that page.

## What is Microsoft Copilot?

Microsoft Copilot is an AI assistant offered as a standalone chat product
and also embedded across Windows, the Microsoft 365 apps, and Edge,
which makes "is Copilot down" a genuinely ambiguous question depending on
which surface someone actually means. This page watches the dedicated
web app, since it is the clearest single, checkable signal without
overreaching into claims about every place Copilot appears.

The gap between the standalone web app and Copilot embedded inside
Microsoft 365 apps is the first thing worth separating. The embedded
experience inside Word, Excel, or Outlook depends on organisational
licensing and each app's own connection to Copilot's backend, which is a
different integration path from the web app most consumers use directly.
A licensing configuration that has not fully propagated, or a desktop app
that has not updated in a while, can make the embedded experience
unreliable while the standalone web app works without any trouble.

Incomplete or cut-off responses are a specific source of confusion that
is often not a platform issue at all. Long or complex prompts can hit
response length limits on their own, and something as ordinary as a
browser tab losing focus or a momentary network hiccup can interrupt a
response mid-stream in a way that looks identical to the model simply
stopping. Retrying the same prompt is usually enough to tell a one-off
interruption from a genuine, persistent problem.

Copilot shares infrastructure with other Microsoft AI features without
being identical to any of them, which means an incident specific to the
chat experience does not automatically extend to Bing search, Windows
features, or the core Microsoft 365 apps, and an issue in one of those
does not necessarily reach Copilot either. Treating each as its own
surface with its own availability is more accurate than assuming a
single incident explains everything at once.

Re-verification prompts are worth ruling out before suspecting an
outage. Microsoft's security systems can require signing in again after
a new device, an unfamiliar location, or a policy change, entirely
independent of whether Copilot's services are running normally.
Completing that check is a security measure functioning as intended, not
evidence that anything is actually down.

## Frequently asked questions

### Is Microsoft Copilot down right now?

Check the board above; it reflects our own probes against Copilot's web app from all five of our regions, refreshed every couple of minutes and confirmed across two regions before this page would call it down.

### Copilot works in the browser but not inside Word or Excel. Is that an outage?

Usually not. Copilot embedded inside Microsoft 365 apps depends on your organisation's licensing and on the specific app's own connection to Copilot's backend, which is a separate integration point from the standalone web app. A licensing gap, an admin setting that has not propagated yet, or an outdated version of the desktop app can all block the embedded experience while the standalone app works normally.

### My response was cut off or Copilot gave an incomplete answer. Is that a platform problem?

Occasionally, but usually not. Long or complex requests can hit response length limits, and a browser tab losing focus or a flaky connection can interrupt a response mid-stream in ways indistinguishable from the model simply stopping. Retrying the same prompt is the fastest way to tell a one-off hiccup from something more persistent.

### Does a Copilot outage affect Bing search or other Microsoft products?

Not necessarily. Copilot shares infrastructure with other Microsoft AI features but is not identical to any of them, so an incident specific to Copilot's chat experience does not automatically mean Bing search, Windows, or Microsoft 365's core apps are affected, and the reverse is also true.

### I keep getting bounced back to a sign-in verification screen. Should I be worried about an outage?

Almost never. Microsoft's security systems can require re-verification after a new device, an unusual sign-in location, or a security policy update, independent of whether Copilot's own services are healthy. Completing the verification resolves it; it is a security control working as intended, not a symptom of downtime.