Retro screen-print illustration: a long line of envelopes with little legs stuck behind a striped barrier on a winding road under a storm cloud, while a small-business owner sits beside an empty mailbox checking his watch.

Not Getting Email Replies? It Might Not Be You: Microsoft Went Down

Clients suddenly silent? On January 22, 2026, a Microsoft 365 outage held up Outlook email for hours. Here's what happened, how to check Microsoft 365 service health yourself, and what to do before you resend.

You sent the quote. You sent the follow-up. Nobody wrote back, and the inbox has been oddly quiet all afternoon.

Before you decide the client went cold, check whether Microsoft is having a bad day. On January 22, 2026, it was.

The quick answer

  1. Check Microsoft's status page at status.cloud.microsoft (no sign-in needed).
  2. If you're the Microsoft 365 admin, check admin.microsoft.com > Health > Service health for an active Exchange Online or Outlook incident.
  3. If there's an incident, don't resend everything. Wait for Microsoft to post that service is restored.
  4. Once it's fixed, check your Outbox and Sent Items, and resend only what's still missing.
  5. Anything urgent in the meantime: pick up the phone.

What happened on January 22, 2026

Here's what was reported at the time. Microsoft posted the detailed updates inside customers' admin centers, so the details below come from its status updates as quoted in news coverage.

  • When: the trouble started on the afternoon of January 22 (U.S. Eastern time) and ran into January 23. The Register reported it dragged on for nearly 10 hours.
  • What broke: Outlook and Exchange Online email, plus Teams, Microsoft Defender, Microsoft Purview and admin tools (TechRadar, 9to5Mac). Some users saw a "451 4.3.2 temporary server issue" error when sending or receiving mail.
  • Where: North America. Microsoft said a "portion of service infrastructure in North America" wasn't "processing traffic as expected."
  • Why: Microsoft's later update blamed elevated load on reduced capacity while it was doing maintenance on part of that North America infrastructure (Tom's Guide). The incident was tracked as MO1221364 in the Microsoft 365 admin center.
  • How many people noticed: thousands of reports on Downdetector within the first hour. Counts in the coverage vary, so we're not putting a number on it.

So yes. For an afternoon, it really did look like everybody was ignoring you.

How to tell if it's Microsoft or just you

Step 1: Check Microsoft's public status page

Go to status.cloud.microsoft. Anyone can open it, no account needed. Microsoft points people there when they can't sign in to check the admin center (Microsoft Learn).

Microsoft also posts on X at @MSFT365Status.

Step 2: Check Service health in the admin center

This is the better view, because it shows incidents affecting your organization, not just the headline ones. You need an admin account (Global Administrator, Global Reader, Service Support admin or Helpdesk admin can all see it).

  1. Sign in at admin.microsoft.com.
  2. Go to Health > Service health. Or select the Service health card on the Home page.
  3. Look under Active issues Microsoft is working on. Click an issue to see what's affected, the status and the updates.
  4. Check Exchange Online and Microsoft 365 suite first. That's where email problems show up.

If you can't sign in to the admin center at all, that's a clue in itself. Go back to Step 1. (Microsoft Learn: How to check Microsoft 365 service health)

Step 3: If Microsoft says everything's fine

Then the problem's probably closer to home. Check:

  • Your Outbox. Messages sitting there never left your computer. Usually that's Outlook being offline or a connection problem on your end.
  • The error message, if you got one. A code starting with 4 (like 451 4.3.2) means a temporary problem. A code starting with 5 means the message was rejected (Microsoft Learn).
  • The other person's side. Their spam or quarantine folder, or their own email provider having a problem. Our post on finding out if incoming business emails are being filtered or hidden covers that.

Fixes, easiest first

1. Don't panic-resend

During an outage, resending the same message five times just means the client gets five copies later.

A "4" error is temporary, and Exchange Online keeps retrying. For mail going out to other servers, it keeps trying for up to 24 hours before it gives up and sends you a failure notice (Microsoft Learn: error 4.4.7). A lot of delayed mail arrives on its own once the service recovers.

2. Use another channel for anything urgent

Phone, text, or a quick note from a personal address if it really can't wait. Keep it short:

"Hi [name], our email is having trouble today because of a Microsoft outage. If you've sent us anything since this morning, we may not have it yet. Call me at [number] if it's urgent."

3. After service is restored, check what actually went

  • Open Outbox. Send anything still stuck.
  • Open Sent Items and compare it to what you meant to send that day.
  • Ask anyone expecting something important whether it arrived.

4. If you're the admin: trace the missing messages

Message trace shows whether a message was delivered, failed, or is still being retried.

  1. Go to the Exchange admin center at admin.exchange.microsoft.com.
  2. Select Mail flow > Message trace.
  3. Search by sender, recipient and time window.
  4. Look at the status. Delivered means it got there. Pending means delivery is still being attempted. Failed means it didn't (Microsoft Learn: Message trace).

Message trace needs Exchange admin or Global Administrator rights. Trace data can take anywhere from 10 minutes to an hour to show up after a message is sent (Microsoft Learn).

Why outages like this happen

Microsoft 365 runs on shared infrastructure. When part of it gets overloaded, every business on it feels it at once. You can't fix it from your end. And moving to a different provider doesn't make you immune: AWS and Cloudflare have both had big outages too.

What you can control is how fast you know about it, and what your team does next.

Preventing the panic next time

Run this once, this week.

  • Get alerts by email. In Health > Service health, select Customize > Email, turn on Send me email notifications about service health, and add up to two addresses. Pick Exchange Online and the services you rely on (Microsoft Learn). Use an address that isn't on Microsoft 365, or you'll get the alert after the outage is over.
  • Install the Microsoft 365 Admin app on the admin's phone for push notifications.
  • Bookmark status.cloud.microsoft on every work computer.
  • Write a one-line staff rule: "If email seems off, check the status page before you troubleshoot or resend."
  • Keep a contact list outside email. Phone numbers for your top clients and vendors, somewhere you can reach when Outlook can't.

When to get help

  • Email has been "slow" or "weird" for days, and Microsoft's status page shows nothing.
  • You're seeing 5.x.x bounce errors, or clients say your mail is going to their spam.
  • Nobody in the business has the admin login, so nobody can check Service health or run a message trace.

Those are worth a second pair of eyes. Reach out if you'd like ours.

Originally published February 2026. Updated October 2026.

No comments yet

Managed Nerds Weekly

Get the week's posts in one email

New IT, security and SEO posts every Monday. That's it.