Microsoft 365 Outage Full Timeline: Exchange Online Down for 17+ Hours in Incident EX1550543 — Microsoft Reports Improving Stability but Still No Fix Date

Tech · 2026-11-13 · By H.A

Microsoft 365 Outage Full Timeline: Exchange Online Down for 17+ Hours in Incident EX1550543 — Microsoft Reports Improving Stability but Still No Fix Date

Every update in Microsoft's EX1550543 and MO1550821 incidents, from the first mailbox errors at 20:17 Mauritius time (16:17 UTC) on 12 November to Friday morning's first signs of lasting recovery, plus the suspected cause, affected services and why there is still no resolution time.

Where Things Stand Right Now

Updated about 13:30 Mauritius time (09:30 UTC) on Friday, 13 November 2026.

The Microsoft 365 outage that started on Thursday is still not resolved. It has now run for more than 17 hours. Microsoft tracks it as two incidents in the Microsoft 365 admin center:

There is cautious good news. At 10:12 Mauritius time (06:12 UTC) Microsoft said it was still recovering its frontend servers while rolling out further traffic optimisation. At 11:44 Mauritius time (07:44 UTC) it reported "positive results for service stability and increased capacity" from its latest traffic optimisation actions, and said it was applying them more broadly across affected regions to reach a persistent recovery. Some users report Outlook loading again, but slowly.

Microsoft has still not given an estimated time of resolution and has not marked either incident as "Service restored". Recovery so far has been partial and has fallen over before, so it is too early to call it fixed. Microsoft has also said there is no indication of malicious activity. Everything it has published points to an internal capacity and connection-handling failure, not a cyberattack.

This article sets out the full timeline, what Microsoft has said about the cause, which services are affected, and what to expect next. All times are Mauritius time (UTC+4), with UTC in brackets.

Before the Outage: A Separate Teams Problem First

A short, unrelated Teams incident came first. Microsoft tracked it as TM1550488, and it ran from 18:45 to 19:53 Mauritius time (14:45 to 15:53 UTC) on 12 November. It was resolved within about an hour. Microsoft has not linked it to the Exchange Online incident, so it should not be counted as part of the main outage.

Timeline: Thursday, 12 November

20:17 Mauritius time (16:17 UTC): official start. Microsoft's estimated start time for EX1550543. Users in the Americas began failing to reach Exchange Online mailboxes through several connection methods at once.

20:20 Mauritius time (16:20 UTC): investigation opens. Microsoft confirmed it was looking into mailbox access problems.

20:55 Mauritius time (16:55 UTC): scope defined. After reviewing telemetry, Microsoft listed the affected access paths: Outlook on the web (OWA), MAPI, Exchange ActiveSync (EAS) and REST.

21:45 Mauritius time (17:45 UTC): first technical clue. Microsoft reported connectivity errors on the infrastructure that handles access requests and began collecting network logs.

21:54 Mauritius time (17:54 UTC): public acknowledgement. Microsoft's public status channel confirmed it was investigating reports from the Americas.

22:07 Mauritius time (18:07 UTC): global warning. Microsoft warned the impact could affect users "in any region". Outage reports on public tracking sites rose sharply around this point. Outlook reports passed 100,000 at the peak, and Microsoft 365 reports reached the tens of thousands.

22:19 Mauritius time (18:19 UTC): "elevated load". Microsoft said part of its infrastructure was under elevated load across multiple regions. It began restarting and repairing servers and considered redirecting traffic.

22:26 Mauritius time (18:26 UTC): MO1550821 opens. Microsoft opened the wider advisory, warning that users might also be unable to connect to Teams, SharePoint Online, Microsoft 365 Copilot and Defender XDR.

22:29 to 22:57 Mauritius time (18:29 to 18:57 UTC): traffic moved. US traffic was redirected away from the affected infrastructure first. Outlook traffic was then redistributed across Microsoft's worldwide infrastructure while affected servers were restarted.

23:06 Mauritius time (19:06 UTC): deployments frozen. Microsoft paused all deployments and configuration changes as a precaution and began reviewing recent changes.

23:18 Mauritius time (19:18 UTC): the cause is not traffic. Microsoft corrected its earlier explanation. The load did not come from more users. A large number of servers had become unexpectedly unavailable, leaving the remaining servers to carry their work.

23:43 to 23:57 Mauritius time (19:43 to 19:57 UTC): health checks blamed. Microsoft said the servers were failing automated health checks and so were being taken out of service. It said the failures might originate in "a specific component that's responsible for processing server health". At this stage it said it had found no recent change that lined up with the start of impact. It stopped further servers from being removed, tested a bypass for the health check, and looked into high CPU usage. Planner and To Do were added to the list of affected services.

Timeline: Friday, 13 November

00:38 Mauritius time (20:38 UTC): fix hard to confirm. Many servers were so unresponsive that Microsoft could not confirm whether its change was working. It began restarting servers with the change applied.

00:56 Mauritius time (20:56 UTC): first real progress. Microsoft validated an alternative health-check method on a subset of servers, which let them return to service. It began a wider rollout and prepared an automated process to detect and restart unresponsive servers. Purview was added to the impact list.

01:20 Mauritius time (21:20 UTC): impact widens. Intune, Defender for Office 365 and Power BI were added.

01:31 Mauritius time (21:31 UTC): config rollback considered. Microsoft said it was assessing whether reverting "a small number of recent configuration updates" could speed up recovery.

02:00 Mauritius time (22:00 UTC): escalation. Microsoft admitted its actions "have not provided the anticipated relief". It said a core process on affected servers is becoming overwhelmed, causing capacity loss. It said it was "opening all available pathways to restore service", isolating parts of the infrastructure and considering isolating whole regions.

02:57 Mauritius time (22:57 UTC): limited recovery. Some servers were back in service and holding stable, and traffic was moved to alternate routes where possible. Microsoft applied protective traffic limits in one location. Universal Print was added.

03:29 Mauritius time (23:29 UTC): Windows 365 affected. Cloud PCs in tenants that use Purview Customer Key were added to the impact list.

03:59 Mauritius time (23:59 UTC): recovered servers fall over again. Microsoft said servers it had returned to service could fail again once traffic hit them. It limited some traffic types by location and rebuilt a subset of servers on a previous configuration.

04:00 to 04:45 Mauritius time (00:00 to 00:45 UTC): scope clarified. Microsoft narrowed MO1550821 to features that depend on Exchange Online and email, and published a revised impact list for each service.

05:06 Mauritius time (01:06 UTC): root cause comes into focus. Microsoft said a process that establishes secure connections on the affected servers becomes overwhelmed, so the servers stop processing requests. It also identified a network configuration change that correlates with the start of impact and began reverting it. This contradicts its earlier statement that no recent change lined up with the onset.

05:45 Mauritius time (01:45 UTC): positive results. Microsoft reported "positive results" from restarting affected infrastructure and recovering servers "in an isolated manner", and began monitoring for stability.

06:09 Mauritius time (02:09 UTC): capacity added. Capacity improvements were applied where possible.

06:54 Mauritius time (02:54 UTC): setback. Microsoft said the changes were not working as expected and that it had identified alternate ways to restore capacity. Teams, Microsoft Graph and Intune impacts were expanded.

07:34 Mauritius time (03:34 UTC): no sign of attack. Microsoft began reviewing traffic flows and routing and stated there was no indication of malicious activity. Defender for Office 365 impacts were expanded.

08:10 Mauritius time (04:10 UTC): partial recovery, not sustained. Microsoft adjusted traffic protocols, redistributed traffic and applied "strategic blocking". It saw partial recovery in some regions, but the recovery did not hold.

Around 08:56 Mauritius time (04:56 UTC): scaling up. Microsoft described a surge in outbound call volume from its routing services to backend servers, driven by the traffic rebalancing it had carried out. It said it was scaling up virtual machines, fixing machines stuck in a bad state, and forcing those machines to sync the recent network change. It set the next updates for 10:00 Mauritius time (06:00 UTC) and 10:30 Mauritius time (06:30 UTC).

10:12 Mauritius time (06:12 UTC): frontend recovery. Microsoft said it was continuing to recover its frontend servers while implementing further traffic optimisation actions to improve stability and increase capacity, and pointed customers to MO1550821 for a fuller update.

11:44 Mauritius time (07:44 UTC): first signs of lasting recovery. Microsoft reported "positive results for service stability and increased capacity" from its latest traffic optimisation actions. It said it was rolling these actions out more broadly across affected regions as it seeks persistent recovery. This is the most encouraging update since the outage began, but Microsoft has not said service is restored.

What Caused It (So Far)

Microsoft has not published a root cause yet. Based on its own updates, the most likely sequence is:

  1. A recent network configuration change (which Microsoft now says correlates with the start of impact) left servers in a bad state.
  2. On those servers, the process that sets up secure connections became overwhelmed, so the servers stopped answering requests.
  3. Automated health checks marked the servers as failed and removed them from service. The remaining servers took on their load and started failing too, which made the outage spread.
  4. Recovery efforts then created their own problem. Rebalancing traffic produced a surge of calls from the routing layer to the backend, which pushed servers that had just recovered back over the edge.

This is a classic cascading failure: self-healing automation and traffic shifting meant to protect the service ended up making things worse. Microsoft's final post-incident review should confirm or correct this picture.

Which Services Are Affected

According to Microsoft's revised impact list, the outage is hitting most things that rely on Exchange Online:

The Defender and Purview impact matters for security teams. While it lasts, some email protection, quarantine review and investigation tooling may not behave normally.

When Will It Be Fixed?

Microsoft has still not given an expected resolution time, and no reliable date or hour has been published anywhere. What we know as of about 13:30 Mauritius time (09:30 UTC) on Friday:

Watch the incident IDs in the admin center for the moment Microsoft marks EX1550543 and MO1550821 as "Service restored". That is the official end point and the time that will count for SLA purposes.

Security Risks While Microsoft Is Down

An outage this large is a gift to attackers, even when the outage itself is not an attack:

What IT and Security Teams Should Do Now

You can poll the incident status from a script during the outage with Microsoft Graph:

Connect-MgGraph -Scopes "ServiceHealth.Read.All"
Get-MgServiceAnnouncementIssue -Filter "id eq 'EX1550543' or id eq 'MO1550821'" |
  Select-Object Id, Title, Status, StartDateTime, EndDateTime, LastModifiedDateTime

What Happens Next

Once service is restored, Microsoft normally publishes a preliminary post-incident review (PIR) in the admin center within a few days, and a final report later. The key questions it needs to answer:

For most organisations, this outage is a reminder that mail, chat, files, AI assistants and parts of the security stack now share a single point of failure. Reef Sentinel will update this story when Microsoft confirms the service is fully restored.

COMPUTE NODE · · --:--:--

Fresh cybersecurity news,
daily threat intelligence.

Daily cyber news, live threat intel and exploited CVEs.

Everything in one place

Self-hosted, hardened, and yours.

RUN IT

Local AI console

Chat with a model on your own hardware via Ollama or any OpenAI-compatible server. No cloud, no key.

DEFEND

Cyber threat feed

Automatic daily intel from CISA KEV, NVD & GitHub advisories, a live cyber threat map, and your own notes.

NEWS

News & videos

Articles and updates on pentesting, AI, and cyber — with embedded video, including YouTube. Post your own.

DIRECTORY

Registry

Runtimes, models, MCP servers, agents, and a full security & pentest tooling section.

PUBLISH

Posts

Write, edit, publish, and share articles backed by a real database and your account.

COMMUNITY

Forum

Threads and replies across categories from Models to Hardware to Security.

CODE

Repos

Curated AI and security GitHub repos, plus a shelf for pinning your own.

DOWNLOAD

Skill packs

Agent starters, RAG scaffolds, and defensive security & VAPT report templates.

Registry

Runtimes, models, MCP servers, agent frameworks, and a security & pentest tooling section — all links out to the real projects.

Local AI console

Talk to a model running on your own machine through Ollama or an OpenAI-compatible server — your prompts and the model's replies always go straight from your browser to your local model, never through a Reef server. Attach files for context, and pick up saved chats where you left off.

Type /image a prompt in the box below to generate
Not connected

Local AI hardware benchmark

A spec-based compatibility advisor — tells you which local models your hardware can run well, which will be slow, and which to skip. Connect to Ollama below for a real, measured speed test instead of an estimate.

1. Your hardware

2. Live check against your local model server (optional)

If a local model server is running, this cross-references the table above with what you've actually got loaded — and runs a real, measured speed test instead of an estimate.

AI Database

A browsable catalog of AI models across providers — context windows, pricing, and capabilities.

Loading…

Cyber threat feed

Latest threats pulled automatically every day from CISA's Known-Exploited-Vulnerabilities catalog and NVD — plus threat intel you post yourself.

⇩ Export STIX
Loading threat feed…

Cyber threat map

Attacks happening right now, all over the world.

Connecting…
LIVE · MAURITIUS TIME--:--:--
attack route, country to country attack route into Mauritius attacker reported worldwide
Loading live data…
attackers reported per minute · click to rewindnow

Top attack routesweb

Attackers based inlast hour

Networkslast hour

Click any dot, feed row or table row to see that IP's profile.

Mauritius

Who attacks Mauritius

Loading…

Web attacks malicious requests to Mauritian websites that were blocked
Network DDoS floods meant to knock Mauritian servers offline

    Mauritius · last 24 h

    How Mauritius is attacked

    Network-level attacks (DDoS) aimed at Mauritius, by method. They try to knock servers and networks offline by sheer volume.

    • Loading…

    The ports or services these floods aimed at aren't published.

    Mauritius · last hour

    Attackers located in Mauritius

    0attackers located in Mauritius were reported in the last hour

    This counts attacks coming from Mauritius, not attacks on it: IPs in Mauritius that servers elsewhere reported for attacking them. Usually zero or one; when it rises, it's often a hacked local server or router.

    Worldwide today

    What attackers are knocking on

    Ports most targeted across a worldwide network of sensors .

    Worldwide today

    Most active attackers

    Ranked by how many separate sensors they hit. Click a row for its profile.

    IPCountryNetworkSensors hitReports
    What you're looking at
    Blue routes

    Share of attack traffic from one country to another. Thicker, faster streams carry more. Particles show volume, not one per attack.

    Every 15 min · published 1–2 h behind
    Amber flashes

    An attacking IP that servers around the world reported in the last minute, placed where the IP is. Its targets aren't published, so there's no line.

    Every minute · shown about 1 min behind
    Locations

    IP locations are approximate (city level at best) and show where the machine is hosted, not who controls it.

    Approximate · city level at best

    News

    Articles, guides and updates on pentesting, AI, and cybersecurity — with embedded video. Add your own, including YouTube.

    Loading…

    Posts

    Loading…

    Loading posts…

    Forum

    Questions, answers, and talk about running AI locally.

    Loading forum…

    GitHub repositories

    Curated AI and security repos, plus your own pinned shelf.

    Command board

    One-liners, configs, and advice worth keeping — shared by everyone here.

    ⚠ Commands are shared with all users. Never include credentials, tokens, or internal hostnames. Review anything before you run it.
    Loading commands…

    Skill packs

    Starter files served from the API — AI agent scaffolds plus defensive security & VAPT reporting templates. Click to download.

    Loading skills…

    Your watchlist

    Follow threat actors, malware, CVEs and vendors — we tell you when a new report, CVE record or exploitation alert mentions them.

    Threat Library

    Threat actors, malware and tools — their attack techniques, Reef Sentinel coverage and indicators of compromise.

    Loading…

    Threat Intelligence

    Curated threat write-ups, advisories and analysis — with cover media.

    Loading…

    Tutorials

    Step-by-step guides for running local AI, using the console, and tracking threats. Admins can add their own.

    Loading…

    Downloads

    Direct links to the official homepage/download page for well-known cybersecurity, penetration-testing, and local-AI software. Always verify checksums/signatures from the vendor before running anything.

    Loading…

    Privacy Policy

    Loading…

    Terms & Conditions

    Loading…

    Help & FAQ

    Answers to common questions about Reef Sentinel, plus a formatting guide for posts, articles, and comments.


    Formatting guide

    Commands you can type into the body of a post, comment, or reply — no HTML needed. Comments and short replies only support bold, italic, and inline code.

    Contact us

    Questions, feedback, or a security disclosure? Reach us directly, or send a message and we'll get back to you by email.

    Loading…

    Send a message

    VAPT Report Generator

    Build an engagement, add findings with a live CVSS calculator, and generate a branded, print-ready report.

    Recon Toolkit

    Investigate any domain, IP, URL, file hash, email or CVE in one search, plus breach and password checks, hash identification and a payload cheatsheet.

    Outage Monitor

    Is Microsoft 365, Facebook, Google, AWS or ChatGPT down? Live status of the big tech services from their official status pages, every incident with its full timeline, and how long each one took to fix.

    Website Checker

    Reads a website's HTTP response headers to identify its framework and server, shows any known CVEs for the exposed versions with details, and recommends what to do.

    Control panel

    Manage everything shown on the site — news & videos, posts, homepage headlines, and subscribers. Admin only.

    Overview
    Content
    Site
    Account & Security

    Email settings

    SMTP on ports 25/465/587 is blocked outbound by some hosts (e.g. DigitalOcean droplets by default) — Resend and Brevo send over their HTTPS API instead, so they work even then. Only the selected provider is used to send; the others stay saved but idle, so you can switch back any time without losing settings.

    Get a key from resend.com/api-keys. Uses the "From address" below as the sender — it must be on a domain you've verified with Resend.

    Get an API key (not an SMTP key) from app.brevo.com/settings/keys/api. Uses the "From address" below as the sender — it must be a verified sender in your Brevo account.

    "From address" and "Site name/URL" are shared by SMTP, Resend, and Brevo — they control what recipients see, regardless of which provider is active.

    Send a test email

    Sends through whichever provider is currently active above. Save your settings first if you just changed them.

    SIGNAL LOST

    We couldn't find this page

    The page may have been moved or deleted, or the address was mistyped.