A laptop displays email alongside cloud synchronization status and an analytics chart in a bright office.
Is Outlook down again? Probably not in the way the headlines suggest. A small jump in Downdetector complaints on November 16 has brought back "Outlook outage today" stories, only two days after Microsoft said it had fixed a large Microsoft 365 failure. What happened earlier in the week was real and well documented. The new spike is a much weaker signal, and it needs to be read separately.

A laptop displays email alongside cloud synchronization status and an analytics chart in a bright office. What the new report says​

The Sunday Guardian reported that Downdetector logged 138 Outlook-related reports at 10:36 a.m., against what it called a usual baseline of three. It describes that as more complaints than normal. It also says the numbers "do not independently confirm a widespread outage."

The report has some gaps:

  • No time zone. The article went up at 06:32 UTC on November 16, which is 1:32 a.m. US Eastern. So "10:36 a.m." can't be Monday morning in the US. The most likely reading is a timestamp from another region, but the article doesn't say. That matters for a story pitched as "Is Outlook down today in the US?"
  • No symptom breakdown. It mentions trouble opening inboxes, sending, loading mail and syncing, then admits the report count can't show which of these people actually had.
  • No geography for the new spike. The countries it lists (the US, the UK, India and New Zealand) come from previous disruption reports, not from the November 16 data.
  • One user quote that doesn't connect. The only user comment, about having no contact with "Pilot Randy" for over 48 hours, has no clear link to an Outlook problem. It isn't evidence of anything.

Summary: 138 crowd-sourced reports from an unclear time and place are worth noting. They don't show a new outage.

The outage that did happen: November 12–14​

Last week's incident was a different matter. Reuters reported on November 12 that Microsoft said it was "aggressively pursuing all pathways to reduce impact". Reuters counted more than 97,000 Outlook reports on Downdetector at 2:07 p.m. ET, and noted that the real number of affected users could be different. The Sunday Guardian's own timeline puts the Outlook peak at nearly 140,000 reports.

Microsoft tracked the incident under two IDs. Its status account pointed admins to EX1550543 and MO1550821 in the Microsoft 365 admin center, as well as status.cloud.microsoft if the admin center is not available. During the worst of it, Microsoft said a core process on affected servers is becoming overwhelmed, causing capacity loss. It also started redistributing connection traffic across our broader worldwide infrastructure to help balance the load.

The damage went well beyond Outlook. A Japanese university help desk copied Microsoft's incident record into its own notice. That record lists Exchange Online, the wider Microsoft 365 suite, Copilot, Defender XDR, Teams and SharePoint Online as affected. One Microsoft 365 service-health tracker also shows a Windows 365 issue: customers who have configured their tenant and Cloud PCs to use Microsoft Purview Customer Key for Windows 365 Cloud PCs may have users who are unable to connect to their Cloud PCs.

What caused it, according to Microsoft​

Microsoft's explanation is short. Its status update said the incident started with a problem during an earlier network capacity upgrade, and that problem only showed up after a later network change. Microsoft says this was a technical issue not related to cyber or AI / agents. It has promised a full post-incident report. Until that's published, anything more specific about the root cause is guesswork.

Regional reporting adds one more detail. Microsoft reportedly said some servers brought back online became unresponsive again once they received traffic, and it extended email timeout limits to 48 hours to preserve delayed messages. That helps explain why recovery took days and not hours.

When it was declared restored​

On November 14, Microsoft said it had completed our efforts to address the underlying issue of the incident and restored service to the remaining impacted customers and regions. It also explained why that took a while: given the scale of demand, we restored services gradually, validating stability at each stage.

A note on dates: depending on the source, the outage started on November 12 or November 13. The Japanese help desk logs the start as November 13 at 03:26, which is almost certainly local time. In the US, that was still the afternoon of November 12. The Sunday Guardian uses both dates. It's the same incident.

Summary: the big outage was real, Microsoft gave a cause, and the company declared it restored on November 14.

Why "restored" doesn't mean every symptom has stopped​

For admins, the most useful lesson is that getting access back and getting mail flowing normally are two separate stages. During recovery, Microsoft warned that customers might be able to sign in again while delivery and processing were still catching up, and that it had no ETA for full recovery at that point.

After the restoration notice, the university's help desk told users that emails delayed during the outage are being processed for delivery sequentially, so emails sent or received during the outage may arrive with a delay even after the service has been restored.

Here's what that looks like in practice. Someone in accounts sent an invoice on Thursday afternoon, and the recipient says it never arrived. It could be stuck in a backlog, bounced after a timeout, or delivered and filed somewhere unexpected. Sending it five more times on Monday fixes none of those, and you may end up with five copies of the invoice in someone's inbox.

What to do if Outlook is misbehaving today​

For home and individual users​

  1. Check Microsoft's public status page (status.cloud.microsoft) before you start fixing your own PC.
  2. Try Outlook on the web. If webmail works and the desktop app doesn't, the problem is probably the app or your device, not Microsoft's service. This narrows things down. It doesn't repair a server-side problem.
  3. Restart the Outlook app and check your internet connection.
  4. Check before you resend. Look in Sent Items and the Outbox, and watch for bounce messages, before sending anything important again.
  5. Contact Microsoft support if the problem continues and nothing shows up on the status page.

For Microsoft 365 administrators​

Microsoft's documentation says to check service health in the Microsoft 365 admin center, under Health > Service health, or on the Service health card on the Home dashboard. The page covers Exchange Online, Teams, Office on the web and other services. Microsoft says the Service Support admin and Helpdesk admin roles can view it. The Issue history tab lists incidents resolved in the last 7 or 30 days, which is where MO1550821 and EX1550543 now appear.

If your tenant is seeing a problem that isn't listed, Microsoft's documentation describes a Report an issue form on the same page. Microsoft says it compares those submissions against data from other organizations to decide whether to open a new incident. If you can't sign in to the admin center at all, Microsoft points to the public status page. During last week's outage it had to fall back on exactly that, posting updates publicly because administrators could not access the Microsoft 365 admin centre.

Summary: check Microsoft's official status first, then test your own setup, and confirm whether a message was delivered before you resend it.

How much weight to give Downdetector​

Downdetector is like a smoke alarm: useful, loud, and sometimes set off by burnt toast. It counts user complaints, not confirmed failures. Hundreds of thousands of reports, matched by Microsoft's own statements and dozens of affected services, is an outage. A spike of 138, with no time zone, no confirmed symptoms and no Microsoft incident, isn't.

There's also a fair point on the other side. Right after a long outage, some leftover problems are likely: delayed mail, stuck sync, and confused users who haven't restarted Outlook since Thursday. A small rise in complaints is exactly what that would look like, and those problems are still a nuisance for the people who have them. They just don't add up to a new global incident.

The Sunday Guardian ends with sensible advice for businesses: have backup ways to communicate, plan for IT contingencies, and don't rely completely on one digital service. Last week showed why. When Exchange, Teams, SharePoint and Copilot all go down together, "just message them on Teams" stops being a fallback.

Bottom line​

  • Confirmed: a major Microsoft 365 outage (MO1550821 / EX1550543) hit Outlook, Teams, Copilot and other services from November 12. Microsoft declared it restored on November 14.
  • Not confirmed: a new Outlook outage on November 16. The 138-report spike is a minor signal with no time zone, no symptoms and no geography attached.
  • Still worth checking: whether messages sent during the outage were delivered or bounced, especially after Microsoft reportedly extended email timeouts to 48 hours.

If Outlook is acting up for you today, check Microsoft's status page and test your own setup before assuming another global outage.

 

References

  1. Microsoft Outlook Outage Today: Is Outlook Down Today in the US? Users Report Email Errors, Receiving, Service Restoration, Website & App Issues | Check Outlook Downdetector Status - The Sunday Guardian The Sunday Guardian 2026-11-16T06:32:26+00:00
  2. Microsoft 365, Outlook down for thousands of US users, Downdetector shows By Reuters investing.com
  3. November 13, 2026 - Microsoft 365 Outage (MO1550821)(Restored) – THERS Account Help Center thersac.icts.thers.ac.jp