Skip to content

Outage tracker / Microsoft 365

Is Microsoft 365 down?

I'm having a problem

Operationalchecked 20 minutes ago

We reached Microsoft 365 from all 4 regions we check.

Functional endpoints verified

Last outage: 10 min on Aug 26, 2026 (sign-in surface, from Europe).

our independent probeslive · checked Sep 3, 2026, 1:09 AM UTC
US-East88 msOperational
US-West319 msOperational
Europe89 msOperational
Asia-Pacific31 msOperational
their status pagetheir claim, not our reading

Microsoft 365 publishes no status feed we can read, so the only independent reading here is ours on the left.

Microsoft 365 response time, by region

US-East
486msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 578ms2026-08-21 UTC: p95 449ms2026-08-22 UTC: p95 432ms2026-08-23 UTC: p95 562ms2026-08-24 UTC: p95 648ms2026-08-25 UTC: p95 563ms2026-08-26 UTC: p95 580ms2026-08-27 UTC: p95 570ms2026-08-28 UTC: p95 611ms2026-08-29 UTC: p95 610ms2026-08-30 UTC: p95 612ms2026-08-31 UTC: p95 610ms2026-09-01 UTC: p95 665ms2026-09-02 UTC: p95 630ms2026-09-03 UTC: p95 486ms
Aug 5Aug 19Sep 3
US-West
500msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 368ms2026-08-21 UTC: p95 513ms2026-08-22 UTC: p95 528ms2026-08-23 UTC: p95 657ms2026-08-24 UTC: p95 524ms2026-08-25 UTC: p95 641ms2026-08-26 UTC: p95 730ms2026-08-27 UTC: p95 590ms2026-08-28 UTC: p95 578ms2026-08-29 UTC: p95 683ms2026-08-30 UTC: p95 545ms2026-08-31 UTC: p95 545ms2026-09-01 UTC: p95 510ms2026-09-02 UTC: p95 602ms2026-09-03 UTC: p95 500ms
Aug 5Aug 19Sep 3
Europe
1.1sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 357ms2026-08-21 UTC: p95 633ms2026-08-22 UTC: p95 614ms2026-08-23 UTC: p95 611ms2026-08-24 UTC: p95 663ms2026-08-25 UTC: p95 611ms2026-08-26 UTC: p95 610ms2026-08-27 UTC: p95 640ms2026-08-28 UTC: p95 621ms2026-08-29 UTC: p95 615ms2026-08-30 UTC: p95 621ms2026-08-31 UTC: p95 679ms2026-09-01 UTC: p95 648ms2026-09-02 UTC: p95 612ms2026-09-03 UTC: p95 1.1s
Aug 5Aug 19Sep 3
Asia-Pacific
1.3sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 1.2s2026-08-21 UTC: p95 1.2s2026-08-22 UTC: p95 1.2s2026-08-23 UTC: p95 1.3s2026-08-24 UTC: p95 1.3s2026-08-25 UTC: p95 1.3s2026-08-26 UTC: p95 1.2s2026-08-27 UTC: p95 1.2s2026-08-28 UTC: p95 971ms2026-08-29 UTC: p95 949ms2026-08-30 UTC: p95 902ms2026-08-31 UTC: p95 835ms2026-09-01 UTC: p95 1.1s2026-09-02 UTC: p95 897ms2026-09-03 UTC: p95 1.3s
Aug 5Aug 19Sep 3

Is it Microsoft 365, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Microsoft 365 -- it cannot diagnose Microsoft 365's own systems.

What we measured, function by function

Microsoft 365 answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the auth row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
  • AuthprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • US-East
    Operationallatency: 88msstatus code: 200checked: Sep 3, 2026, 1:09 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Microsoft 365 normally. We do not have enough reports from US-East to say anything about what people there are seeing.
  • US-West
    Operationallatency: 319msstatus code: 200checked: Sep 3, 2026, 1:09 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Microsoft 365 normally. We do not have enough reports from US-West to say anything about what people there are seeing.
  • Europe
    Operationallatency: 89msstatus code: 200checked: Sep 3, 2026, 1:09 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Microsoft 365 normally. We do not have enough reports from Europe to say anything about what people there are seeing.
  • Asia-Pacific
    Operationallatency: 31msstatus code: 200checked: Sep 3, 2026, 12:58 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Microsoft 365 normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
  • US-Central
    Not monitored from this regionMicrosoft 365 is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionMicrosoft 365 is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionMicrosoft 365 is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionMicrosoft 365 is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionMicrosoft 365 is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionMicrosoft 365 is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Microsoft 365, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Microsoft 365 yet, which is not evidence that nothing is wrong.

Recent outages

Partial outage, 10mmeasured by our probes · Europe2026-08-26

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Microsoft 365 since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Microsoft 365 covering any window you pick, with our measurements and Microsoft 365's own claim at the time, side by side.

Full availability history for Microsoft 365: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Microsoft 365, and again when they can reach it again. That is our own measurement from ten regions, not Microsoft 365's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Microsoft 365 uptime measured by RealUptimeLive, from this page's own readings.
[![Microsoft 365 uptime measured by RealUptime](https://realuptime.io/outages/microsoft-365/badge.svg?days=30)](https://realuptime.io/outages/microsoft-365)
<a href="https://realuptime.io/outages/microsoft-365"><img src="https://realuptime.io/outages/microsoft-365/badge.svg?days=30" alt="Microsoft 365 uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Microsoft 365's SLA implies, from our measurement

At or above your target

We measured none of downtime for Microsoft 365 over the 337h 29m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

Separately, we measured 10 minutes where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.

This is computed from our own probe measurements, not from Microsoft 365's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: auth surface
https://login.microsoftonline.com/common/v2.0/.well-known/openid-configuration
secondary
https://status.cloud.microsoft/
RealUptime is not affiliated with Microsoft 365; the name identifies what we measured, and nothing here speaks for Microsoft 365's own team. We send a single web request to Microsoft 365 from 4 regions on our own schedule and time the response. We do not see inside Microsoft 365's systems, do not use an account or real transaction, and are not the same signal Microsoft 365's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Microsoft 365 is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Microsoft 365 operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. Read the full methodology.