{"id":426721,"date":"2026-01-22T22:06:11","date_gmt":"2026-01-22T22:06:11","guid":{"rendered":"https:\/\/www.newsbeep.com\/ca\/426721\/"},"modified":"2026-01-22T22:06:11","modified_gmt":"2026-01-22T22:06:11","slug":"microsoft-down-live-updates-on-outage-affecting-365-office-outlook-teams-and-more","status":"publish","type":"post","link":"https:\/\/www.newsbeep.com\/ca\/426721\/","title":{"rendered":"Microsoft down \u2014 live updates on outage affecting 365, Office, Outlook, Teams and more"},"content":{"rendered":"

Refresh <\/p>\n

2026-01-22T21:55:14.454Z
\nSlow recovery<\/p>\n

As mentioned previously, reports have been in decline but it’s slow, suggesting that recovery is happening but not everyone has been able to access their Outlook emails or 365 services.<\/p>\n

2026-01-22T21:46:58.492Z
\nStatus page still crashing<\/p>\n

Microsoft is telling people to go to its status page<\/a> for updates but it continues to be affected by the 429 error, which means too many are trying to access the page.<\/p>\n

Several Tom’s Guide readers have commented that they can’t access the status page.<\/p>\n

I’ve been able to access it through brute force persistent refreshing.<\/p>\n

2026-01-22T21:28:37.513Z
\n<\/p>\n

\n

\"Microsoft\n<\/p>\n

(Image credit: Down Detector)<\/p>\n

Since Microsoft announced that it was redirecting traffic and implemented a repair reports have quickly dropped on Down Detector.<\/p>\n

That doesn’t mean the outage is over since thousands of reports are still coming in, they’ve just lessened.<\/p>\n

Outlook, the most affected service, is still above 10,000 reports though it is in decline.<\/p>\n

2026-01-22T21:20:24.352Z
\nInfrastructure restored says Microsoft<\/p>\n

While we’ve restored the affected infrastructure to a heathy state, further load balancing is required to mitigate impact. We’re directing traffic to alternate infrastructure to achieve recovery. More information can be found at https:\/\/t.co\/uFnnN6T3jN or under MO1221364 if\u2026January 22, 2026<\/a><\/p>\n

Microsoft says it has restored the infrastructure to a “healthy state” with a caveat.<\/p>\n

The company says it still needs “further load balancing” to mitigate the impact from the outage. Traffic is being redirected while the fix goes into effect.<\/p>\n

2026-01-22T21:13:22.161Z
\nUp and down reports<\/p>\n

Reports for Outlook have plateaued <\/a>but other services are a mixed bag. Some services like Azure went down but are spiking again.<\/p>\n

365 is dipping a bit and Store is going up. Teams meanwhile is going down.<\/p>\n

2026-01-22T21:00:37.482Z
\nMicrosoft update<\/p>\n

We’re continuing to review what actions are required to restore the affected infrastructure to a heathy state and rebalance the service traffic to achieve recovery. More information can be found at https:\/\/t.co\/uFnnN6T3jN or under MO1221364 if accessible.January 22, 2026<\/a><\/p>\n

Another tweet from Microsoft just went up. Unfortunately, there isn’t anything new here.<\/p>\n

“We’re continuing to review what actions are required to restore the affected infrastructure to a heathy state and rebalance the service traffic to achieve recovery.”<\/p>\n

It’s similar to the message we’ve seen on the status page. However, access to the status page is intermittent due to the 429 errors, so sharing this message in multiple places is getting people some information.<\/p>\n

2026-01-22T20:53:42.055Z
\nWhere we stand after just over an hour<\/p>\n

\n

\"Microsoft\n<\/p>\n

(Image credit: Down Detector)<\/p>\n

This outage kicked off around 11 a.m. Pacific but didn’t really hit until closer to 11:40 am.<\/p>\n

Right now, reports on Down Detector <\/a>have started to dip a little across every Microsoft service. However, we are still seeing a high numbers including over 12,000 reports for Outlook, close 16,000 reports for 365, and 2,700 reports for Store.<\/p>\n

The status page<\/a> hasn’t changed, and Microsoft hasn’t tweeted in about 35 minutes.<\/p>\n

However, the company says it is continuing to review the incident to determine what actions it needs to restore service.<\/p>\n

2026-01-22T20:47:52.212Z
\n365 seems to work but not Outlook<\/p>\n

\n

\"The\n<\/p>\n

(Image credit: Shutterstock)<\/p>\n

I’m seeing comments on Down Detector and social media that some people are able to login to the admin center for Microsoft 365.<\/p>\n

Outlook appears to be having more problems with claims of emails not sending or receiving. I’ve seen some comments from users who can send emails but aren’t receiving any new ones.<\/p>\n

2026-01-22T20:41:29.681Z
\nIntermittent interruption<\/p>\n

I was able to load the status page again, but it won’t stay up. Refreshing causes the 429 error to hit.<\/p>\n

There is some new information, including this message:<\/p>\n

“Users may be receiving a “451 4.3.2 temporary server issue” error message when attempting to send or receive email through Outlook.”<\/p>\n

The update does say that users may experience intermittent impact.<\/p>\n

2026-01-22T20:34:20.220Z
\nStatus page crashes!<\/p>\n

\n

\"Microsoft\n<\/p>\n

(Image credit: Microsoft)<\/p>\n

Either because of the infrastructure issues or due to a fix Microsoft is attempting to implement, the Status page is also now down.<\/p>\n

When I try to access it I keep getting the above error message.<\/p>\n

An HTTP 429 Error refers to a site receiving too many requests. I’m sure it’s not just me trying to access the page.<\/p>\n

2026-01-22T20:27:37.375Z
\nCause identified<\/p>\n

We’ve identified a portion of service infrastructure in North America that is not processing traffic as expected. We’re working to restore the infrastructure to a healthy state to achieve recovery. More information can be found at https:\/\/t.co\/uSHwRmXFJZ or under MO1221364 if\u2026January 22, 2026<\/a><\/p>\n

Microsoft says it has identified a cause for the outage.<\/p>\n

“We’ve identified a portion of service infrastructure in North America that is not processing traffic as expected. We’re working to restore the infrastructure to a healthy state to achieve recovery,” the company posted in a tweet<\/a>.<\/p>\n

On the status page<\/a>, it provided a little more a details saying that the infrastructure is impacting load balancing and service availability.<\/p>\n

2026-01-22T20:22:59.295Z
\nStatus page update<\/p>\n

\n

\"Microsoft\n<\/p>\n

(Image credit: microsoft)<\/p>\n

The official Microsoft status page has finally updated. It specifically notes service degradation for Microsoft 365 (Business or Enterprise).<\/p>\n

Surprisingly, the page reads, “Users may be seeing degraded service functionality across multiple Microsoft 365 services.”<\/p>\n

That message would normally appear in the admin center, but apparently the outage may affect some people’s ability to even access the admin center.<\/p>\n

The message says people may have issues with sending and receiving emails.<\/p>\n

2026-01-22T20:18:06.162Z
\nMixed bag for Microsoft apps<\/p>\n

Over on Down Detector, Outlook, 365, Teams and Microsoft Store are seeing a growing number of reports.<\/p>\n

On the other hand, Azure and Defender XDR spiked but have quickly started to decline. It’s possible these services aren’t as affected compared to the big apps like 365.<\/p>\n

2026-01-22T20:09:14.780Z
\nSimilar to previous outage?<\/p>\n

During the outage on Jan 21, Microsoft blamed the interruption on an issue related to a third-party. It’s believed that an unnamed ISP caused connections between Microsoft’s services and the apps.<\/p>\n

This led to user unable to login to 365 or Teams or in some cases even open the app.<\/p>\n

2026-01-22T20:02:36.525Z
\nMicrosoft acknowledges outage<\/p>\n

We’re investigating a potential issue impacting multiple Microsoft 365 services, including Outlook, Microsoft Defender and Microsoft Purview. Further information can be found in the admin center under MO1221364.January 22, 2026<\/a><\/p>\n

The official Microsoft status page <\/a>hasn’t been updated yet, but the official Microsoft 365 X account <\/a>posted that the company is investigating.<\/p>\n

“We’re investigating a potential issue impacting multiple Microsoft 365 services, including Outlook, Microsoft Defender and Microsoft Purview. Further information can be found in the admin center under MO1221364.”<\/p>\n

2026-01-22T19:56:36.966Z
\nOther services affected<\/p>\n

\n

\"Microsoft\n<\/p>\n

(Image credit: Down Detector)<\/p>\n

While they haven’t received the same number of reports we are seeing other Microsoft services interrupted as well.<\/p>\n

These include Azure, Defender, and Teams.<\/p>\n

2026-01-22T19:54:54.378Z
\nSudden spike <\/p>\n

\n

\"Microsoft\n<\/p>\n

(Image credit: Down Detector)<\/p>\n

The new outage kicked off around noon Pacific with Outlook hitting<\/a> just over 6,750 reports on Down Detector.<\/p>\n

Microsoft 365, the office apps suite, is less but still sitting closer to 4,000 reports<\/a>.<\/p>\n

Please follow our community guidelines<\/a>.”><\/p>\n

You must confirm your public display name before commenting<\/p>\n

Please logout and then login again, you will then be prompted to enter your display name.<\/p>\n

Logout<\/p>\n