Microsoft 365 favicon
Microsoft 365 Status microsoftonline.com

Is Microsoft 365 down?

Microsoftonline.com is currently experiencing an incident

An incident has been reported for Microsoft 365.

The other half

Is it Microsoft 365, or is it you?

This page answers half the question. It tells you about Microsoft 365. It cannot tell you whether your own site is experiencing an incident, and that is the part your users notice. UptimeRobot checks your websites, APIs and servers, and tells you when one of them does.

50 monitors for your own websites. No card.

Current status

Incident

Incident reported 3h 35m 12s ago


Last check

Checked every 5 minutes


Last 24 hours

100%

Checks on provider website have reported 0 incidents, 0m down

Response time

N/A

Average

N/A

Minimum

N/A

Maximum

The response-time chart above shows Microsoft 365's status over time, based on our automated checks. Each point on the chart represents the result of a check run every 5 minutes.

Last 7 days

100%

0 incidents, 0m down

Last 30 days

100%

0 incidents, 0m down


Last 365 days

100%

0 incidents, 0m down

Latest incidents

Root cause
Duration

Microsoft 365: Users may be unable to connect to multiple Microsoft 365 services
—

Microsoft 365: Users report possible problems with Microsoft 365
—

Microsoft 365: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods
—

Microsoft 365: Some users may intermittently receive no response when submitting queries in Microsoft 365 Copilot Chat
3h 58m

Microsoft 365: Some users may experience errors or failures when accessing their mailbox via Outlook on the web
4h 28m

Microsoft 365: Some users may be intermittently unable to send email messages to Outlook.com, Hotmail.com, or Live.com email addresses
3d 11h

Microsoft 365: Users may be unable to view recent portions of their conversation history with Microsoft 365 Copilot Chat
6d 7h

Microsoft 365: External users’ replies to encrypted email messages may not be delivered in Exchange Online
1d 6h

Microsoft 365: Admins were unable to complete Microsoft OneDrive or SharePoint site migrations
4d 21h

Microsoft 365: Some users may see intermittent failures when accessing Exchange Online through Representational State Transfer (REST)
9h 3m

View 2026 Microsoft 365 outage archive →

How our status checker works?

We continuously monitor Microsoft 365 from our own infrastructure to give you an objective view of its status. Every every 5 minutes, we send a request to microsoftonline.com from our primary location in the US and verify that the site responds correctly and within a normal time frame.

If the first check fails, we immediately repeat it from a second location to avoid false positives. When that second attempt also fails, we trigger a third confirmation check from a random global location. Only if all three checks confirm a problem, we mark Microsoft 365 as having an issue or a major outage.

Frequently asked questions

An incident has been reported for Microsoft 365. See Latest incidents below for details.

An incident has been reported for Microsoft 365, so the problem may not be on your side.

Try opening microsoftonline.com from another browser, device, or network (e.g., mobile hotspot). You can also disable your VPN, clear DNS cache, restart your router, or check whether your internet provider is having issues. If the site works elsewhere, the problem is likely local rather than a confirmed Microsoft 365 outage.

We monitor microsoftonline.com from our own infrastructure. When a check fails, we repeat the test from two other randomly chosen global locations to eliminate false positives. If these checks fail too, we mark Microsoft 365 as down.

A Microsoft 365 outage means our checks detected that microsoftonline.com was not responding correctly after multiple checks from different global locations. This doesn't always mean every user is affected. Some outages are regional, some affect only certain features, and some appear as slow loading instead of a full failure.

Not exactly. UptimeRobot monitors microsoftonline.com from the outside, so we can detect when something is wrong and show high-level symptoms such as connection timeouts, HTTP errors, or failed responses from specific regions.

However, we don't have visibility into internal systems, so we can't identify the exact root cause (like a failed deployment, database issue, or infrastructure problem).

What we can show you:

  • When the issue started and when it was resolved
  • How long the outage lasted
  • Which regions were affected
  • The type of error observed (for example, timeouts or HTTP status codes like 500 or 404)

For detailed root cause information and official updates, we recommend checking Microsoft 365's official status page.

Yes, UptimeRobot lets you set up your own monitors for microsoftonline.com so you get alerted the moment something goes wrong, and before your users notice. Our free plan includes 50 monitors with 5-minute check intervals. You'll also get details that this public status page doesn't show, such as response headers, response body, region-level results, and a full activity log.

Create a free UptimeRobot account and set up a monitor for microsoftonline.com. You'll receive alerts via email, SMS, Slack, webhooks, and other integrations as soon as we detect an issue, and again when it's resolved. Because we monitor independently from Microsoft 365's own infrastructure, you may be notified even before their official status page acknowledges the issue.

Alternatively, you can check whether Microsoft 365 offers notifications on its official status page.

Over the last 5 years, the average resolved outage for Microsoft 365 lasted 1d 15h. That average is the mean difference between created_at and resolved_at across 20 resolved incidents we track for this provider.

Over the last 5 years, Microsoft 365 appears on our outage timeline 24 times. Comparable productivity tools averaged 5 incidents in the same period, so Microsoft 365 has more incidents than the average productivity tool.

For the most recent incident where community reports were logged, we recorded 1 user-generated report.

The first user-generated report was logged at 2026-11-12 18:10:35.670 UTC. Microsoft 365's official incident was created at 2026-11-12 16:17:27.723 UTC — 0s later.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.