Skip to content

Outage tracker / Microsoft 365

Is Microsoft 365 down?

I'm having a problem

Checks passingchecked moments ago

Our checks of Microsoft 365 pass from all 10 regions we check.

As of Oct 19, 2026, 8:54 PM UTC, RealUptime's checks of Microsoft 365 passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of Microsoft 365 did not fail from two or more distant regions in the 60 days we have checked it (since Aug 20, 2026). This does not show Microsoft 365 works for users.

Email me when our checks of Microsoft 365 fail from two or more distant regions

One email when our checks of Microsoft 365 fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not Microsoft 365's official status.

our check readinglive · checked Oct 19, 2026, 8:54 PM UTC
US-East594 msChecks passing
US-West1094 msChecks passing
Europe506 msChecks passing
Asia-Pacific953 msChecks passing
US-Central408 msChecks passing
Canada787 msChecks passing
UK380 msChecks passing
Southeast Asia1175 msChecks passing
Australia1615 msChecks passing
South America985 msChecks passing
their status pagetheir claim, not our reading

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

Microsoft 365 response time, by region

US-East
1.1sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 532ms2026-10-06 UTC: p95 538ms2026-10-07 UTC: p95 547ms2026-10-08 UTC: p95 592ms2026-10-09 UTC: p95 569ms2026-10-10 UTC: p95 550ms2026-10-11 UTC: p95 557ms2026-10-12 UTC: p95 557ms2026-10-13 UTC: p95 575ms2026-10-14 UTC: p95 619ms2026-10-15 UTC: p95 685ms2026-10-16 UTC: p95 784ms2026-10-17 UTC: p95 843ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.1s
Sep 20Oct 4Oct 19
US-West
1.3sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 1.1s2026-10-06 UTC: p95 692ms2026-10-07 UTC: p95 736ms2026-10-08 UTC: p95 638ms2026-10-09 UTC: p95 645ms2026-10-10 UTC: p95 650ms2026-10-11 UTC: p95 663ms2026-10-12 UTC: p95 711ms2026-10-13 UTC: p95 708ms2026-10-14 UTC: p95 664ms2026-10-15 UTC: p95 557ms2026-10-16 UTC: p95 607ms2026-10-17 UTC: p95 970ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.3s
Sep 20Oct 4Oct 19
Europe
871msp95 · 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-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 653ms2026-10-06 UTC: p95 657ms2026-10-07 UTC: p95 736ms2026-10-08 UTC: p95 644ms2026-10-09 UTC: p95 630ms2026-10-10 UTC: p95 621ms2026-10-11 UTC: p95 624ms2026-10-12 UTC: p95 607ms2026-10-13 UTC: p95 636ms2026-10-14 UTC: p95 639ms2026-10-15 UTC: p95 626ms2026-10-16 UTC: p95 631ms2026-10-17 UTC: p95 662ms2026-10-18 UTC: p95 724ms2026-10-19 UTC: p95 871ms
Sep 20Oct 4Oct 19
Asia-Pacific
1.6sp95 · 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-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 923ms2026-10-06 UTC: p95 984ms2026-10-07 UTC: p95 952ms2026-10-08 UTC: p95 930ms2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 919ms2026-10-11 UTC: p95 930ms2026-10-12 UTC: p95 986ms2026-10-13 UTC: p95 960ms2026-10-14 UTC: p95 956ms2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.6s
Sep 20Oct 4Oct 19
US-Central
1.3sp95 · 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-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.1s2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 976ms2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 686ms2026-10-15 UTC: p95 991ms2026-10-16 UTC: p95 787ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s
Sep 20Oct 4Oct 19
Canada
969msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 675ms2026-10-06 UTC: p95 878ms2026-10-07 UTC: p95 668ms2026-10-08 UTC: p95 558ms2026-10-09 UTC: p95 633ms2026-10-10 UTC: p95 697ms2026-10-11 UTC: p95 615ms2026-10-12 UTC: p95 673ms2026-10-13 UTC: p95 664ms2026-10-14 UTC: p95 633ms2026-10-15 UTC: p95 580ms2026-10-16 UTC: p95 718ms2026-10-17 UTC: p95 858ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 969ms
Sep 20Oct 4Oct 19
UK
947msp95 · 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-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 837ms2026-10-06 UTC: p95 950ms2026-10-07 UTC: p95 872ms2026-10-08 UTC: p95 898ms2026-10-09 UTC: p95 781ms2026-10-10 UTC: p95 704ms2026-10-11 UTC: p95 678ms2026-10-12 UTC: p95 712ms2026-10-13 UTC: p95 982ms2026-10-14 UTC: p95 822ms2026-10-15 UTC: p95 900ms2026-10-16 UTC: p95 787ms2026-10-17 UTC: p95 921ms2026-10-18 UTC: p95 982ms2026-10-19 UTC: p95 947ms
Sep 20Oct 4Oct 19
Southeast Asia
1.7sp95 · 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-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.9s2026-10-06 UTC: p95 1.7s2026-10-07 UTC: p95 1.7s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 1.8s2026-10-10 UTC: p95 1.8s2026-10-11 UTC: p95 1.9s2026-10-12 UTC: p95 1.7s2026-10-13 UTC: p95 1.8s2026-10-14 UTC: p95 1.7s2026-10-15 UTC: p95 1.8s2026-10-16 UTC: p95 1.7s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.7s
Sep 20Oct 4Oct 19
Australia
2.3sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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.6s2026-10-06 UTC: p95 1.6s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 2.1s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.3s
Sep 20Oct 4Oct 19
South America
1.9sp95 · 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-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.3s2026-10-06 UTC: p95 1.5s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.6s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.9s
Sep 20Oct 4Oct 19

Check your own site while you wait on Microsoft 365

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • AuthprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 594msstatus code: 200checked: Oct 19, 2026, 8:53 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
      Checks passinglatency: 1094msstatus code: 200checked: Oct 19, 2026, 8:53 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
      Checks passinglatency: 408msstatus code: 200checked: Oct 19, 2026, 8:52 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
      Checks passinglatency: 787msstatus code: 200checked: Oct 19, 2026, 8:51 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
    Checks passinglatency: 985msstatus code: 200checked: Oct 19, 2026, 8:52 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 506msstatus code: 200checked: Oct 19, 2026, 8:53 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
      Checks passinglatency: 380msstatus code: 200checked: Oct 19, 2026, 8:53 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 953msstatus code: 200checked: Oct 19, 2026, 8:54 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
      Checks passinglatency: 1175msstatus code: 200checked: Oct 19, 2026, 8:52 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
      Checks passinglatency: 1615msstatus code: 200checked: Oct 19, 2026, 8:50 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 probe events

No probe events on record yet for Microsoft 365.

check 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 check readings and Microsoft 365's own claim at the time, side by side.

Full check history for Microsoft 365: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

Microsoft 365 uptime by RealUptime's checksLive, from this page's own readings.
[![Microsoft 365 uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Microsoft 365 down?", https://realuptime.io/outages/microsoft-365. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

How our checks compare with Microsoft 365's stated SLA

At or above your target

Our checks of Microsoft 365 failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, 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/

What our check can and cannot see

A pass means the configuration document the service publishes, such as an API or sign-in description, loaded. That document is usually static or cached, so it does not show that the endpoints it describes are answering.

Host checked: login.microsoftonline.com

RealUptime is not affiliated with Microsoft 365; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.