Skip to content

Outage tracker / Microsoft 365 / In the US

Is Microsoft 365 down in the US?

Checks passingin the US, measured from Ashburn, San Jose, and Chicago

All 3 of our probes in the US, in Ashburn, San Jose, and Chicago, read checks passing when they last checked Microsoft 365 at Nov 5, 2026, 2:26 PM UTC.

Over the last 24 hours we completed 1361 checks from Ashburn, San Jose, and Chicago and 1358 answered cleanly, 99.77% availability.

Of the 7 other regions we check Microsoft 365 from, all 7 read checks passing right now.

Email me the next time we see Microsoft 365 go down

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.

What our Ashburn, San Jose, and Chicago probes measured

AshburnChecks passing578 checks in 24h, 100.00%
San JoseChecks passing428 checks in 24h, 100.00%
ChicagoChecks passing355 checks in 24h, 99.15%

Last checked Nov 5, 2026, 2:26 PM UTC.

Microsoft 365 from Ashburn, San Jose, and Chicago over the last 30 days

Over the last 30 days, Microsoft 365 answered our Ashburn probe in 499 ms on average, and 1 check in 20 took longer than 823 ms.

Over the last 30 days, Microsoft 365 answered our San Jose probe in 575 ms on average, and 1 check in 20 took longer than 968 ms.

Over the last 30 days, Microsoft 365 answered our Chicago probe in 583 ms on average, and 1 check in 20 took longer than 1,167 ms.

Ranked by average response time across the 10 cities we check Microsoft 365 from, Ashburn 3rd, San Jose 4th, Chicago 6th; Frankfurt was fastest at 325 ms and Sydney slowest at 1,163 ms.

From Ashburn, San Jose, and Chicago we ran 50,780 checks of Microsoft 365 in 30 days, and 50,767 answered cleanly: 99.97% availability.

8 of the 30 days had at least one failed check. The weakest was Nov 4 (UTC), at 99.77% across 1,344 checks.

In Ashburn local time (EST), Microsoft 365 was slowest around 9 PM, at 691 ms on average over the last 14 days, and quickest around 10 AM, at 497 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 5797100.00%694 ms
Wed, Nov 41,34499.77%647 ms
Tue, Nov 31,316100.00%671 ms
Mon, Nov 21,613100.00%656 ms
Sun, Nov 11,794100.00%598 ms
Sat, Oct 311,796100.00%602 ms
Fri, Oct 301,795100.00%616 ms
Thu, Oct 291,79199.94%615 ms
Wed, Oct 281,79499.94%593 ms
Tue, Oct 271,79299.94%611 ms
Mon, Oct 261,79599.83%668 ms
Sun, Oct 251,79499.88%626 ms
Sat, Oct 241,798100.00%628 ms
Fri, Oct 231,800100.00%621 ms

Microsoft 365 outages measured from the US

Our Ashburn, San Jose, and Chicago probes measured no confirmed Microsoft 365 outage in the last 90 days.

How the other regions read right now

Of the 7 other regions we check Microsoft 365 from, all 7 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 386 checks
TokyoChecks passing100.00% of 240 checks
TorontoChecks passing100.00% of 357 checks
LondonChecks passing100.00% of 356 checks
SingaporeChecks passing100.00% of 354 checks
SydneyChecks passing100.00% of 349 checks
São PauloChecks passing100.00% of 354 checks

Other countries we check Microsoft 365 from

How we measured this

The US readings on this page come from RealUptime's own Ashburn, San Jose, and Chicago probes against Microsoft 365's public endpoints. They are not user reports, and they are not Microsoft 365's own status page.

See Microsoft 365's full check readings, the 90-day history by region, or the outage tracker methodology.

Check your own site from Ashburn

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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter