Skip to content

Outage tracker / Microsoft 365

Is Microsoft 365 down?

I'm having a problem

Operationalchecked moments ago

We reached Microsoft 365 from all 10 regions we check.

As of Oct 5, 2026, 8:17 PM UTC, Microsoft 365 answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

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

Email me the next time we see Microsoft 365 go down

Measured by our own probes from ten regions, not Microsoft 365's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

our independent probeslive · checked Oct 5, 2026, 8:17 PM UTC
US-East329 msOperational
US-West374 msOperational
Europe104 msOperational
Asia-Pacific294 msOperational
US-Central954 msOperational
Canada494 msOperational
UK145 msOperational
Southeast Asia644 msOperational
Australia99 msOperational
South America1105 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
524msp95 · 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-09-06 UTC: p95 561ms2026-09-07 UTC: p95 578ms2026-09-08 UTC: p95 578ms2026-09-09 UTC: p95 581ms2026-09-10 UTC: p95 687ms2026-09-11 UTC: p95 574ms2026-09-12 UTC: p95 580ms2026-09-13 UTC: p95 562ms2026-09-14 UTC: p95 614ms2026-09-15 UTC: p95 581ms2026-09-16 UTC: p95 754ms2026-09-17 UTC: p95 688ms2026-09-18 UTC: p95 709ms2026-09-19 UTC: p95 663ms2026-09-20 UTC: p95 631ms2026-09-21 UTC: p95 610ms2026-09-22 UTC: p95 580ms2026-09-23 UTC: p95 596ms2026-09-24 UTC: p95 658ms2026-09-25 UTC: p95 596ms2026-09-26 UTC: p95 613ms2026-09-27 UTC: p95 556ms2026-09-28 UTC: p95 643ms2026-09-29 UTC: p95 606ms2026-09-30 UTC: p95 597ms2026-10-01 UTC: p95 689ms2026-10-02 UTC: p95 621ms2026-10-03 UTC: p95 525ms2026-10-04 UTC: p95 564ms2026-10-05 UTC: p95 524ms
Sep 6Sep 20Oct 5
US-West
720msp95 · 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-09-06 UTC: p95 522ms2026-09-07 UTC: p95 537ms2026-09-08 UTC: p95 483ms2026-09-09 UTC: p95 428ms2026-09-10 UTC: p95 379ms2026-09-11 UTC: p95 431ms2026-09-12 UTC: p95 435ms2026-09-13 UTC: p95 471ms2026-09-14 UTC: p95 448ms2026-09-15 UTC: p95 828ms2026-09-16 UTC: p95 934ms2026-09-17 UTC: p95 906ms2026-09-18 UTC: p95 865ms2026-09-19 UTC: p95 883ms2026-09-20 UTC: p95 940ms2026-09-21 UTC: p95 790ms2026-09-22 UTC: p95 742ms2026-09-23 UTC: p95 553ms2026-09-24 UTC: p95 733ms2026-09-25 UTC: p95 869ms2026-09-26 UTC: p95 914ms2026-09-27 UTC: p95 970ms2026-09-28 UTC: p95 888ms2026-09-29 UTC: p95 824ms2026-09-30 UTC: p95 748ms2026-10-01 UTC: p95 747ms2026-10-02 UTC: p95 711ms2026-10-03 UTC: p95 707ms2026-10-04 UTC: p95 697ms2026-10-05 UTC: p95 720ms
Sep 6Sep 20Oct 5
Europe
653msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 659ms2026-09-07 UTC: p95 674ms2026-09-08 UTC: p95 685ms2026-09-09 UTC: p95 649ms2026-09-10 UTC: p95 697ms2026-09-11 UTC: p95 740ms2026-09-12 UTC: p95 799ms2026-09-13 UTC: p95 804ms2026-09-14 UTC: p95 743ms2026-09-15 UTC: p95 693ms2026-09-16 UTC: p95 613ms2026-09-17 UTC: p95 604ms2026-09-18 UTC: p95 612ms2026-09-19 UTC: p95 629ms2026-09-20 UTC: p95 620ms2026-09-21 UTC: p95 662ms2026-09-22 UTC: p95 641ms2026-09-23 UTC: p95 671ms2026-09-24 UTC: p95 659ms2026-09-25 UTC: p95 688ms2026-09-26 UTC: p95 693ms2026-09-27 UTC: p95 711ms2026-09-28 UTC: p95 719ms2026-09-29 UTC: p95 698ms2026-09-30 UTC: p95 665ms2026-10-01 UTC: p95 662ms2026-10-02 UTC: p95 628ms2026-10-03 UTC: p95 704ms2026-10-04 UTC: p95 651ms2026-10-05 UTC: p95 653ms
Sep 6Sep 20Oct 5
Asia-Pacific
922msp95 · 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-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 1.0s2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 988ms2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 904ms2026-09-12 UTC: p95 925ms2026-09-13 UTC: p95 876ms2026-09-14 UTC: p95 930ms2026-09-15 UTC: p95 971ms2026-09-16 UTC: p95 944ms2026-09-17 UTC: p95 948ms2026-09-18 UTC: p95 913ms2026-09-19 UTC: p95 1.0s2026-09-20 UTC: p95 986ms2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 944ms2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 970ms2026-10-02 UTC: p95 790ms2026-10-03 UTC: p95 927ms2026-10-04 UTC: p95 951ms2026-10-05 UTC: p95 922ms
Sep 6Sep 20Oct 5
US-Central
1.1sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 930ms2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 874ms2026-09-11 UTC: p95 892ms2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 1.0s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 604ms2026-09-16 UTC: p95 788ms2026-09-17 UTC: p95 770ms2026-09-18 UTC: p95 745ms2026-09-19 UTC: p95 756ms2026-09-20 UTC: p95 762ms2026-09-21 UTC: p95 708ms2026-09-22 UTC: p95 951ms2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 914ms2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 963ms2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 921ms2026-10-01 UTC: p95 863ms2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 973ms2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
Canada
655msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 607ms2026-09-07 UTC: p95 619ms2026-09-08 UTC: p95 734ms2026-09-09 UTC: p95 695ms2026-09-10 UTC: p95 596ms2026-09-11 UTC: p95 530ms2026-09-12 UTC: p95 574ms2026-09-13 UTC: p95 568ms2026-09-14 UTC: p95 496ms2026-09-15 UTC: p95 500ms2026-09-16 UTC: p95 711ms2026-09-17 UTC: p95 713ms2026-09-18 UTC: p95 769ms2026-09-19 UTC: p95 722ms2026-09-20 UTC: p95 760ms2026-09-21 UTC: p95 826ms2026-09-22 UTC: p95 764ms2026-09-23 UTC: p95 618ms2026-09-24 UTC: p95 636ms2026-09-25 UTC: p95 641ms2026-09-26 UTC: p95 665ms2026-09-27 UTC: p95 606ms2026-09-28 UTC: p95 617ms2026-09-29 UTC: p95 659ms2026-09-30 UTC: p95 601ms2026-10-01 UTC: p95 696ms2026-10-02 UTC: p95 704ms2026-10-03 UTC: p95 606ms2026-10-04 UTC: p95 647ms2026-10-05 UTC: p95 655ms
Sep 6Sep 20Oct 5
UK
824msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 790ms2026-09-07 UTC: p95 700ms2026-09-08 UTC: p95 716ms2026-09-09 UTC: p95 697ms2026-09-10 UTC: p95 796ms2026-09-11 UTC: p95 864ms2026-09-12 UTC: p95 833ms2026-09-13 UTC: p95 891ms2026-09-14 UTC: p95 953ms2026-09-15 UTC: p95 821ms2026-09-16 UTC: p95 687ms2026-09-17 UTC: p95 677ms2026-09-18 UTC: p95 354ms2026-09-19 UTC: p95 602ms2026-09-20 UTC: p95 599ms2026-09-21 UTC: p95 767ms2026-09-22 UTC: p95 740ms2026-09-23 UTC: p95 823ms2026-09-24 UTC: p95 963ms2026-09-25 UTC: p95 926ms2026-09-26 UTC: p95 915ms2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 835ms2026-09-29 UTC: p95 946ms2026-09-30 UTC: p95 920ms2026-10-01 UTC: p95 898ms2026-10-02 UTC: p95 738ms2026-10-03 UTC: p95 733ms2026-10-04 UTC: p95 880ms2026-10-05 UTC: p95 824ms
Sep 6Sep 20Oct 5
Southeast Asia
1.8sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.4s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.3s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.6s2026-09-23 UTC: p95 1.9s2026-09-24 UTC: p95 2.1s2026-09-25 UTC: p95 2.1s2026-09-26 UTC: p95 2.2s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 2.1s2026-09-29 UTC: p95 2.1s2026-09-30 UTC: p95 1.9s2026-10-01 UTC: p95 1.9s2026-10-02 UTC: p95 1.8s2026-10-03 UTC: p95 1.8s2026-10-04 UTC: p95 1.8s2026-10-05 UTC: p95 1.8s
Sep 6Sep 20Oct 5
Australia
1.6sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.7s2026-09-07 UTC: p95 1.7s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.7s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.6s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.6s2026-09-15 UTC: p95 1.5s2026-09-16 UTC: p95 1.7s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.7s2026-09-19 UTC: p95 1.6s2026-09-20 UTC: p95 1.6s2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 1.7s2026-09-23 UTC: p95 1.6s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.6s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 1.6s
Sep 6Sep 20Oct 5
South America
1.3sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.5s2026-09-07 UTC: p95 1.5s2026-09-08 UTC: p95 1.4s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.5s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 1.6s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.6s2026-09-18 UTC: p95 1.6s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.3s
Sep 6Sep 20Oct 5

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: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • AuthprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
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

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 329msstatus code: 200checked: Oct 5, 2026, 8:16 PM 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: 374msstatus code: 200checked: Oct 5, 2026, 8:15 PM 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.
    • US-Central
      Operationallatency: 954msstatus code: 200checked: Oct 5, 2026, 8:16 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Microsoft 365 normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 494msstatus code: 200checked: Oct 5, 2026, 8:17 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Microsoft 365 normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 1105msstatus code: 200checked: Oct 5, 2026, 8:16 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Microsoft 365 normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 104msstatus code: 200checked: Oct 5, 2026, 8:15 PM 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.
    • UK
      Operationallatency: 145msstatus code: 200checked: Oct 5, 2026, 8:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Microsoft 365 normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 294msstatus code: 200checked: Oct 5, 2026, 8:16 PM 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.
    • Southeast Asia
      Operationallatency: 644msstatus code: 200checked: Oct 5, 2026, 8:15 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Microsoft 365 normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 99msstatus code: 200checked: Oct 5, 2026, 8:16 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Microsoft 365 normally. We do not have enough reports from Australia to say anything about what people there are seeing.

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.

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 last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

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

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 10 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. Read the full methodology.