How Microsoft Is Bringing Microsoft 365 Back: Rollbacks, Extra Capacity and Careful Traffic Control After 17+ Hours of Exchange Online Failures

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

How Microsoft Is Bringing Microsoft 365 Back: Rollbacks, Extra Capacity and Careful Traffic Control After 17+ Hours of Exchange Online Failures

Microsoft is reverting a network change, rebuilding server capacity and throttling traffic to end the EX1550543 outage, and reported its first signs of lasting recovery at 11:44 Mauritius time (07:44 UTC) on 13 November, but still has no fix time.

Where Things Stand

As of about 13:30 Mauritius time (09:30 UTC) on Friday, 13 November 2026, the Microsoft 365 outage that began at 20:17 Mauritius time (16:17 UTC) on Thursday is still not officially over. Microsoft has not marked either incident, EX1550543 (Exchange Online) or MO1550821 (the wider Microsoft 365 advisory), as "Service restored", and it has not given an estimated time for full recovery.

There is, however, real progress. At 11:44 Mauritius time (07:44 UTC) Microsoft reported "positive results for service stability and increased capacity" from its latest traffic optimisation work, and said it was rolling those actions out more broadly across affected regions to reach a persistent recovery. That is the first time since the outage began that Microsoft has talked about recovery that lasts, rather than recovery that collapses again under load. Some users are reporting that Outlook loads again, although slowly.

Microsoft has also said repeatedly that there is no indication of malicious activity. This is an internal capacity failure, not a cyberattack.

This article explains what Microsoft is actually doing to bring the service back, step by step, and why it has taken so long. All times are Mauritius time (UTC+4), with UTC in brackets.

What Broke, in Short

Microsoft has not published a final root cause, but its own updates describe a clear chain of events:

  1. A recent network configuration change lines up with the start of the outage. Microsoft first said it had found no matching change, then at 05:06 Mauritius time (01:06 UTC) on Friday said it had identified one and began reverting it.
  2. On the affected Exchange Online servers, the process that sets up secure connections became overwhelmed, so the servers stopped answering requests.
  3. Automated health checks saw those servers failing and removed them from service. The servers that were left took on their traffic, became overloaded too, and the failure spread.
  4. Later, the work to rebalance traffic caused a surge of calls from Microsoft's routing layer to backend servers, which knocked recently recovered servers back over.

Everything Microsoft is doing now is aimed at breaking that chain: stop more servers falling out, remove the trigger, rebuild capacity, and let traffic back in slowly enough that it does not knock the service down again.

Step 1: Stopping the Damage From Spreading

The first job was to stop the outage getting worse.

These steps limited the spread, but they did not fix the underlying fault. Servers that came back kept failing again.

Step 2: Undoing the Trigger

With simple restarts not holding, Microsoft turned to the changes that might have caused the failure.

Rolling back a change across a global fleet is slow. Every server has to receive the fix, restart cleanly and prove it is healthy before it can take real traffic again.

Step 3: Rebuilding Capacity

Because so many servers dropped out at once, Microsoft also needs more working capacity than usual to absorb the backlog of users trying to reconnect.

Step 4: Controlling the Traffic

The hardest part of this recovery has been traffic. Every Outlook client, phone and Teams app in the affected regions keeps retrying, so as soon as servers come back they are hit with a wave of reconnections.

To manage that, Microsoft has:

At 11:44 Mauritius time (07:44 UTC), Microsoft said these latest traffic optimisation actions were producing better stability and more capacity, and it began applying them across all affected regions.

Why Recovery Keeps Stalling

The outage has now passed 17 hours because each fix has run into the same wall: servers come back, get flooded, and fall over again.

At 06:54 Mauritius time (02:54 UTC), Microsoft admitted its changes were "not taking as expected" and said it faced "sustained traffic management imbalances". Its later explanation was that the rebalancing work itself caused a surge in outbound calls from routing services to backend servers.

This is a familiar pattern in large outages, sometimes called a thundering herd: millions of clients retry at the same moment, and the rush of reconnections becomes a second outage. The only reliable fix is to bring capacity back gradually, region by region, while holding traffic back just enough that recovered servers can stay up. That is what Microsoft's latest updates describe.

What "Restored" Will Look Like

When the service does come back, it is unlikely to be a single moment:

What You Should Do While It Recovers

Reef Sentinel will keep following the recovery and update its coverage 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.