Check a site
Check a website Service status Outages Blog
All tools
Check a websiteBrowse all tools
Outages · live

1 outage happening now.

Every outage here was confirmed by our own measurements, by a moderator, or by the provider on its own status page. A spike in user reports alone never puts a service on this page.

1Happening now
0Recovering
0Resolved · 14 days
20Provider reports
Microsoft 365microsoft365.com
Major Ongoing

Users may be unable to connect to multiple Microsoft 365 services.

Listed for
16 h 18 min
Listed since
Source
Microsoft’s status page
Updates
25
Latest update ·

Microsoft: Current status: We remain focused on addressing residual impact and ensuring reliable service restoration. We continue to assess recovery across various connection methods and are closely monitoring service health to verify sustained stability. At this time, we have no evidence of malicious activity associated with this incident. We will continue to treat this with urgency until full mitigation, and we will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation is complete. Next update by: Friday, November 13, 2026, at 6:00 PM UTC

Microsoft names 14 services
  • Exchange Online
  • Microsoft Teams
  • SharePoint Online
  • Microsoft Copilot 365
  • Microsoft Defender XDR
  • Microsoft Planner
  • Microsoft To Do
  • Microsoft Intune
  • Microsoft Defender for Office 365
  • Microsoft Purview
  • Power BI
  • Microsoft 365 Apps Admin Center
  • Universal Print
  • Windows 365
Provider saysOutage reportedMicrosoft 365 status
Our check Up · 841 msmicrosoft365.com ·

Our check only loads microsoft365.com from our server. Signed-in services can fail while the website answers.

  1. OngoingMicrosoft: Current status: We remain focused on addressing residual impact and ensuring reliable service restoration. We continue to assess recovery across various connection methods and are closely monitoring service health to verify sustained stability. At this time, we have no evidence of malicious activity associated with this incident. We will continue to treat this with urgency until full mitigation, and we will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation is complete. Next update by: Friday, November 13, 2026, at 6:00 PM UTC
  2. OngoingMicrosoft: Current status: Current status: We remain focused on addressing residual impact and ensuring reliable service restoration. We continue to assess recovery across various connection methods and are closely monitoring service health to verify sustained stability. At this time, we have no evidence of malicious activity associated with this incident. We will continue to treat this with urgency until full mitigation, and we will share a full Post-Incident Report with root cause and defense-in-depth actions after mitigation is complete. Next update by: Friday, November 13, 2026, at 6:00 PM UTC
  3. OngoingMicrosoft: Current status: We're observing sustained improvements in service availability as recovery progresses across affected Microsoft 365 services. While service functionality continues to improve, some users may still experience intermittent connectivity issues or delayed email delivery. Our efforts are increasingly focused on resolving the remaining issues and restoring consistent service for all affected users. We're validating recovery across different connection methods and monitoring service stability to confirm that improvements are… Next update by: Friday, November 13, 2026, at 4:00 PM UTC

Also reported by providers

From their own status pages. Not confirmed by us and not counted above.

See all 20 on the status board

Updated · this page refreshes itself every minute

The last 14 days

1 confirmed incident, from our measurements, moderators and providers’ own pages

  1. Sat
    31
    Sat 31 Oct: no incidents
  2. Sun
    1
    Sun 1 Nov: no incidents
  3. Mon
    2
    Mon 2 Nov: no incidents
  4. Tue
    3
    Tue 3 Nov: no incidents
  5. Wed
    4
    Wed 4 Nov: no incidents
  6. Thu
    5
    Thu 5 Nov: no incidents
  7. Fri
    6
    Fri 6 Nov: no incidents
  8. Sat
    7
    Sat 7 Nov: no incidents
  9. Sun
    8
    Sun 8 Nov: no incidents
  10. Mon
    9
    Mon 9 Nov: no incidents
  11. Tue
    10
    Tue 10 Nov: no incidents
  12. Wed
    11
    Wed 11 Nov: no incidents
  13. Thu
    12
    Thu 12 Nov: no incidents
  14. 1 Fri
    13
    Fri 13 Nov: 1 incident (Microsoft 365)
Days with an outage
1/14
Major
1
Minor
0
Longest resolved
—

Resolved

Nothing resolved in the last 14 days. The open incident above will move here once it’s over.

Right now on our checks

Our own latest request to each of 64 services’ websites, newest . This is a separate signal from the outages above.

Status board
  • 64 up
  • 0 having issues
  • 0 down
  • 0 not measured in 2 h

Most popular services

Outage alerts and news

What happened, from official sources, and what to do about it.

The blog

How an outage gets on this page

  1. 01

    Detect

    Our server requests each service in the catalogue on a schedule. When three samples in a row find a service down or failing, it opens a private incident candidate: a major one when the service is unreachable, a minor one when it answers with errors or very slowly.

  2. 02

    Confirm

    A person then checks the candidate. Only confirmed incidents are listed here, with a timeline of what we saw. Rejected candidates are never shown, and a burst of user reports on its own never puts a service on this page.

  3. 03

    Follow the provider

    A few providers publish their own incidents in a public feed we read every two minutes (Microsoft). When one of them reports an incident on its own status page, it is listed here too, marked as reported by the provider, with each of the provider’s updates on its timeline.

  4. 04

    Resolve

    An incident moves from Investigating to Ongoing while the problem lasts, then Recovering once the service answers again, and Resolved when it stays healthy. A provider’s incident closes once its page has stayed clear for 15 minutes. Resolved incidents stay listed for 14 days.

Not listed? Find the service’s status page for its latest check, or check any website from our server.

Cookies on UtiBox

UtiBox is free because of ads. Google and its partners use cookies to show, limit and measure ads, Google Analytics, Ahrefs Web Analytics and Microsoft Clarity show us how the site is used, and we use a few essential cookies to run the site.