Service degradation on Microsoft 365 (status.cloud.microsoft)

589 points by dkpk 9 hours ago

pwthornton 2 hours ago

Nadella stripped mined the company for AI jank, and everything has been falling apart. Github has been unreliable a lot lately. Xbox is basically imploding. A lot of Azure, Entra, Intune, etc. is shockingly janky, and there is clearly very little investment in it.

llama052 2 hours ago

I’d imagine they are going to get a massive drain of whatever talent is left from their company wide severance as well.

We use Azure at work and it’s wild how much stuff is just manual labor behind the scenes on their platform.

Seems like it’s always on fire somewhere, ripe for burnout and MBOs aren’t aligned with reality from what I hear.

stogot a few seconds ago

What is MBO?

rsalus an hour ago

There are huge swaths of azure engineering teams that deploy things entirely manually via azure portal. Insane.

beoberha 2 minutes ago

senderista 44 minutes ago

> We use Azure at work and it’s wild how much stuff is just manual labor behind the scenes on their platform.

AWS is no different. Everything is on fire all the time, but customers usually don't notice.

mrdootdoot 16 minutes ago

juujian an hour ago

Hadn't heard about Xbox, what's happening?

OnlineTux an hour ago

Massive layoffs and studio closures and mergers like Obsidian merged with Bethesda.

New Xbox to cost $1200-$1800.

Gamepass limited to 15 hours a month for Ultimate.

djray 14 minutes ago

EmX_3000 38 minutes ago

It'll probably be an app instead of its own thing in the future. For Pluton-enabled systems only of course.

12_throw_away 2 hours ago

I don't know exactly what's going on with today's outage.

But this is certainly exactly what I'd expect after indiscriminately laying off half your workers, then immediately offering a buyout to make sure any experienced people still standing will find their way to the door.

If this incident, or the difficulty they're having with remediation (update: holy shit, they still haven't even identified the problem), are somehow not caused by any of that, then it's at least a preview of what things are going to be like.

kstrauser an hour ago

OTOH, I couldn’t manage Entra without their AI chatbot. That system is a Lovecraftian stack of sadness built upon despair, of which mortals are not meant to know.

nullwarp 44 minutes ago

This really is the honest truth, every interaction I have with the MS platform is somehow worse than an actual dumpster fire. AI is the only thing keeping the ship afloat. Then again maybe that's the point?

Gaussian 28 minutes ago

Janky is part of the Fabric at Microsoft. I don’t feel like that’s new…

AIorNot an hour ago

So a few years ago Nadella was a God among CEOs capturing OpenAI at the right time etc..but yeah laying off thousands of tenured folks surely is great strategy, god I hate the tech industry.

Btw does everyone see how insanely crappy Windows 11 is compared to MacOS

fractal618 an hour ago

I made the switch to Linux Mint and it’s wonderful and almost triples my battery life. I’m also in the process of switching to a phone with graphene os which runs like butter and feels so much more secure, safe and private.

elboru 16 minutes ago

tapland 35 minutes ago

jwilcoxson an hour ago

Yup.

beowulfey 8 hours ago

Copied this from my post in the other thread:

The Status page is not working well, but I managed to subscribe to their RSS feed and it has been sending out updates periodically. I'll post some of them here.

9:02 PM UTC: We've validated an alternative health check method on a subset of affected infrastructure, which allowed the servers in that subset to successfully return to service, and we're now applying this change more broadly. We're also preparing an automated recovery process to continually detect and restart unresponsive servers, to help keep them in service while this change progresses. Additionally, our review of recent changes has identified a small number of configuration updates that we're investigating as potential contributors to the issue.

Previous status: While validating the targeted change, we found that many of the affected servers have become unresponsive, which is preventing us from confirming whether the change is effective. We're restarting these servers so they can come back online with the change in place, and we're applying the same approach to additional affected portions of our infrastructure to validate the results more broadly.

8:52 PM UTC: While validating the targeted change, we found that many of the affected servers have become unresponsive, which is preventing us from confirming whether the change is effective. We're restarting these servers so they can come back online with the change in place, and we're applying the same approach to additional affected portions of our infrastructure to validate the results more broadly.

Previous Status: While we haven't identified any recent changes that correlate with the start of impact, our investigation indicates the failed health checks may originate from a specific component on the affected servers that's responsible for processing them. We're deploying a targeted change to bypass this component on a subset of servers to validate whether this restores availability, and we've taken steps to prevent additional servers from being removed from service while we work to return the affected servers to service. We're also investigating why affected servers are experiencing elevated processor usage while handling requests.

7:52 PM UTC: We've identified that affected servers are failing automated health checks, which is causing them to become unavailable, and this may be related to a recent change to a component involved in processing those checks. We're testing a configuration change on a subset of affected infrastructure to address this and, if successful, will apply it more broadly. In parallel, we've initiated a restart of all affected servers and are validating whether they're successfully returning to service.

7:30 PM UTC: We're aggressively pursuing all pathways to reduce impact. As a precaution, we've paused all deployments and configuration changes while we review recent changes for any correlation to this event. We've determined that the elevated load isn't driven by an overall increase in traffic, but by a large number of servers being unexpectedly unavailable, which is shifting load onto the remaining infrastructure. We're investigating what's causing these servers to become unavailable while we work to safely return them to service.

7:16 PM UTC: We're aggressively pursuing all pathways to reduce impact. As a precaution, we've paused all deployments and configuration changes while we review recent changes for any correlation to this event. We've also moved traffic for some services off the affected infrastructure to further reduce load, with additional traffic moves in progress.

6:59 PM UTC: We've completed redistributing connection traffic across our worldwide infrastructure, and we're moving additional traffic off the affected infrastructure to further reduce load. We're also restarting affected servers to return them to service. In parallel, we're investigating whether the elevated traffic reflects a genuine increase in requests or a shift in how traffic is being routed across our infrastructure.

no-dr-onboard 7 hours ago

This is like getting transmissions from Cassini before it falls into saturn.

hammock 5 hours ago

Why is there not a single mention that this could be a cyberattack? Is the issue only affecting the USA?

outworlder 4 hours ago

testrun 4 hours ago

lazyasciiart 5 hours ago

Prickle 3 hours ago

colechristensen 3 hours ago

King-Aaron 3 hours ago

gosub100 2 hours ago

elmo2you 5 hours ago

razingeden an hour ago

Cortana, play My Heart Will Go - oh.

EvanAnderson 7 hours ago

I feel bad for the people working on this. It sounds like desperation is increasing.

From the 10:11:39 PM UTC update:

Current status: We're continuing to pursue all available pathways to restore service, as our actions taken thus far have not provided the anticipated relief. Our investigation has found that a core process on the affected servers is becoming overwhelmed, which causes the servers to stop responding and contributes to the capacity loss.

To validate a potential recovery approach, we're fully isolating a portion of our service infrastructure, restarting the affected components, and gradually reintroducing traffic to confirm our services remain stable before applying this approach more broadly. We're also analyzing traffic patterns across our entire service infrastructure and evaluating whether isolating traffic within each region may allow affected regions to recover independently.

From the 9:41:46 PM UTC update:

Current status: We're continuing to work through restarting and validating the affected servers to safely return them to service, and we're exploring opportunities to expedite this process. In parallel, we're assessing whether reverting the small number of recent configuration updates we identified could help accelerate recovery.

From the 9:01:14 PM UTC update:

Current status: We've validated an alternative health check method on a subset of affected infrastructure, which allowed the servers in that subset to successfully return to service, and we're now applying this change more broadly. We're also preparing an automated recovery process to continually detect and restart unresponsive servers, to help keep them in service while this change progresses. Additionally, our review of recent changes has identified a small number of configuration updates that we're investigating as potential contributors to the issue.

From the 8:44 PM UTC update:

Current status: While validating the targeted change, we found that many of the affected servers have become unresponsive, which is preventing us from confirming whether the change is effective. We're restarting these servers so they can come back online with the change in place, and we're applying the same approach to additional affected portions of our infrastructure to validate the results more broadly.

Previous Status: While we haven't identified any recent changes that correlate with the start of impact, our investigation indicates the failed health checks may originate from a specific component on the affected servers that's responsible for processing them. We're deploying a targeted change to bypass this component on a subset of servers to validate whether this restores availability, and we've taken steps to prevent additional servers from being removed from service while we work to return the affected servers to service. We're also investigating why affected servers are experiencing elevated processor usage while handling requests.

NolF an hour ago

This seems like the same terse language/feedback OpenAI models give me and I leave more clueless than I arrived.

EvanAnderson 5 hours ago

Working in reverse-chronological order here:

From the 1:06:17 AM UTC update:

Current status: Our investigation has found that a process on the affected servers responsible for establishing secure connections becomes overwhelmed, causing the servers to stop processing requests. We're preparing a configuration change to address this behavior that can be applied across all affected servers, and we're validating it on a subset of servers before applying it more broadly alongside restarts of the affected infrastructure. In parallel, we've begun reverting a recent network configuration change that correlates with the start of impact and are monitoring to determine whether this contributes to recovery.

The temporary traffic limitations we previously described are now in effect in specific locations. We're monitoring the affected servers in those locations to confirm whether they remain stable while handling a narrower set of connections, after which we'll gradually reintroduce additional traffic.

---

The list of impacted services just grew tremendously.

From the 12:56:09 AM UTC update:

Features of the Microsoft 365 services below that interact with Exchange Online and email services are impacted. Elements of those services that do not depend on interaction with Exchange Online remain functional.

- Exchange Online: Users may be unable to access their mailbox using Outlook on the web, Outlook desktop (MAPI), Exchange ActiveSync (EAS), or REST-based connections, and email delivery may be delayed.

- Microsoft 365 admin center: Admins may be unable to load some admin center pages.

- Microsoft 365 apps: Users may be unable to view their recently used files.

- Microsoft 365 Apps Admin Center: Multiple services including Cloud Update, Cloud Policy, and Inventory are affected.

- Microsoft 365 Education: Features including Assignments, Reading Progress, and Speaker Progress may be impacted.

- Microsoft Copilot 365: Users may be unable to load Copilot Chat or receive responses in the web and desktop apps, and Copilot experiences may be unable to access work data such as email, calendar, and files.

- Microsoft Defender for Office 365: Safe Links may be unable to verify URLs, which may impact users clicking links in Outlook and Teams.

- Microsoft Defender XDR: Users may be unable to load Microsoft Defender portal pages or solution tabs.

- Microsoft Fabric: Users may encounter failures when exporting reports with sensitivity labels to PDF or PowerPoint, or when updating artifacts with sensitivity labels.

- Microsoft Graph: API requests that access Exchange Online data, such as mail, calendar, and contacts, may time out.

- Microsoft Intune

- Microsoft Planner: Users are experiencing Plan and Task operation reliability issues.

- Microsoft Purview: Multiple Purview services including Authorization, auto-labeling, Data Loss Prevention (DLP), Communication Compliance, and Data Classification are impacted, and users may be unable to load Microsoft Purview portal pages.

- Microsoft Teams: Scenarios that depend on Exchange Online, including calendar, meeting scheduling, and creating chats for organizations using Information Barriers, may fail. Core messaging and online meetings remain largely functional.

- Microsoft To Do: The app may not load, and users may see operation failures.

- Power BI: All users may intermittently be unable to export reports with MIP sensitivity labels to PDF in Power BI.

- SharePoint Online: Features that depend on Exchange Online may be impacted. Accessing files stored directly in SharePoint Online remains functional.

- Universal Print: Users may encounter errors submitting print jobs or using admin features.

- Windows 365: 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.

Current status: We've reviewed known impact scenarios and have revised the list of impact services and features, which can be viewed in the "more info" section of this communication.

We're continuing our work to isolate the issue affecting server availability, as well as other workstreams.

---

So much for seeming hopeful.

From the 12:08:53 AM UTC update:

Current status: While the servers we've returned to service initially remain healthy, we've observed that they can become unresponsive again once they begin receiving traffic. We're analyzing diagnostic data from these servers with our networking and platform experts to determine what's triggering this behavior.

Building on the protective traffic management measures we've implemented, we're also temporarily limiting which types of traffic can reach the affected infrastructure in specific locations. This will help us determine whether a particular type of request is contributing to the impact and allow us to restore service incrementally. Additionally, we're rebuilding a subset of affected servers using a previous software configuration to validate whether this prevents them from becoming unresponsive, and we'll expand this approach to additional servers if we observe positive results.

---

The 11:05:31 PM UTC update is is the first since the outage began that feels hopeful.

From the 11:06:31 PM UTC update:

Current status: We've begun returning a portion of the affected servers to service, and they're remaining stable so far. We've also shifted traffic and connections to alternative pathways wherever possible and have observed limited recovery in some regions.

We've streamlined our recovery process to expedite returning the remaining affected servers to service. To further support recovery, we're implementing protective traffic management measures in a specific location to reduce load on the affected infrastructure, and we'll expand these measures to additional locations if we observe positive results. As capacity is restored, users may experience a gradual recovery as their clients reconnect to the service.

EvanAnderson 2 hours ago

matt3210 4 hours ago

Sounds like nobody knows how their own systems work anymore.

hn_throwaway_99 3 hours ago

riffic 3 hours ago

netsharc 3 hours ago

fock 5 hours ago

their employer brought me agent swarms supposed to take over my php-serving machines. whatever this is, I don't feel sorry for them.

trebligdivad 3 hours ago

Nah, they're just debugging a hard problem while the world looks on! The 'normal' problems they have processes to work through, but hey emergent systems and all that - they have to expect the unexpected.

reaperducer 5 hours ago

Ugh. There's some yahoo from NewsNation on WGN Radio right now saying this is because of the Chinese, and obliquely linking it to Nvidia.

Reddit-level speculation.

llama052 4 hours ago

piker 5 hours ago

So the thundering herd wins again

eddythompson80 6 hours ago

they are furiously typing at their agents hoping they can figure out what to do. Getting glimps of hope everytime claude says "I found it." only for their hopes to be crused at "Turns out ...". The clown show at Microsoft is surreal.

Rantenki 5 hours ago

wmchen 8 hours ago

Not really a big deal, but it is presently 8pm UTC time. I'm curious why their RSS feed seems to be 2 hours off?

beowulfey 8 hours ago

Ah no that was a mistake on my part! RSS Feed was in EST and I misremembered the difference

SubiculumCode 3 hours ago

Gonna have to rebrand as Office364

jwilcoxson an hour ago

Well done sir

jiggawatts an hour ago

We already call it Microsoft 356.

Eji1700 5 hours ago

Day 12: It has been 3 days since the last ping returned, I fear I will not make it back to my family. Give my love to dear Liza.

I feel for those stuck in there. The outage going on for this long has got to be fucking brutal.

ArcHound 8 hours ago

They are turning it off and on again. I don't even. If this works, our industry is cooked as the kids say.

onefiftymike 7 hours ago

I worked on multi-million dollar airplanes. If a pilot called me with an issue and hadn't rebooted the plane (on the ground), I wouldn't even talk to them. Rebooting isn't always a bad solution to technology.

ArcHound 7 hours ago

cyberax 7 minutes ago

thisismyanon2 3 hours ago

olyjohn 2 hours ago

taftster 4 hours ago

justonceokay 7 hours ago

In maintenance, sometimes the dumb solution is the best. The servers that ran amazon.com had a memory leak and were subsequently restarted. This hack continues for years because it was the most cost-effective thing to do.

Put another way, if they didn’t turn it off and on again, I would think less of them because that’s the first thing you should always do unless you know better

jimmaswell 7 hours ago

icameron 4 hours ago

Powercycling is a designed method to bailout Cisco routers. If you botch a configuration command and lose connection, you can have someone powercycle it to restore you last good configuration. Its not just a joke it really works more often than I'd like to admit.

macintux 2 hours ago

bawolff 7 hours ago

Amateur hour. Everyone knows professionals say "power cycling" instead to make it sound complicated.

red-iron-pine 5 hours ago

dudus 8 hours ago

So the servers are ok but many of the health checks are failing and so the servers are taken off rotation, increasing load on other servers. I'm sure it's more complicated than it seems but from my POV this looks like amateur hour at Microsoft.

shermantanktop 5 hours ago

Amateur hour? Not sure if you've lived through one of these cascading failures, but they are hard to design against, hard to load/chaos test for, and hard to recover from. The key is that this is a dynamic load, not a static load; and it's normally amplified by uncontrolled retry behavior by clients.

In retrospect, the cause and cure are obvious to everyone.

YZF 2 hours ago

UltraSane 42 minutes ago

llama052 4 hours ago

infamouscow 5 hours ago

mminer237 5 hours ago

Newest update says that wasn't the issue after all. They say relatively small loads are actually causing servers to become unresponsive and have to be restarted.

They still don't know why this "core process" is maxing out the processor for no reason.

SoftTalker 2 hours ago

burningChrome 5 hours ago

This sounds suspiciously what occurred when I was working at a large motor sports company. We had a major release of new year models coming out on the website. The deployment went super smooth and then in about 30 mins the site was crashing. Since we were a huge MS client, almost everything we ran was all MS top to bottom.

Site was taken offline, war rooms ensued. 48 hours later, an Ops team from Redmond was flown out. Another three days and they determined it was several legacy servers were going down and the load balancing servers were getting hit so hard, they also failed. It was a cascading effect that killed everything.

CIO was pissed. The company got absolutely lit up on every social media channel for their ineptitude. The CIO vowed it would never happen again, they were upgrading the entire network and infrastructure to avoid it happening again. Fast forward six months to the next major release. Same thing, same panic, same cascading failures because servers were collapsing under the traffic to the website. Another war room, another Ops team flies out. Two days later they figured out it was some buggy code that was causing it.

This after 8 rounds of load balancing testing to the tune of 10X the amount of traffic the site sees on these major release dates without so much as a hiccup.

I left two months later, but the overall feeling was the same - total amateur hour from Microsoft after our company was gifted major discounts to go all in with their hardware & network gear. The company found out the hard way it wasn't a smart decision.

The scary part was this some 20 years ago - seems like not much has changed considering how frequently Github is down now too.

semiquaver 7 hours ago

The people writing these updates are very obviously not technical and are least one step removed from the actual work being done to fix this.

EvanAnderson 5 hours ago

codingdave 5 hours ago

6031769 7 hours ago

At Microsoft every hour is amateur hour.

mapontosevenths 6 hours ago

bradleyjg 7 hours ago

NoPicklez 4 hours ago

I can't stand it when I see armchair analysts making claims like this.

I'm sure it's more complicated than that.... but from my POV, which is extremely limited and informed by what others online tell me.... that this is amateur hour

What would it take for it to be professional hour?

TheOtherHobbes an hour ago

steve1977 7 hours ago

Copilot hour!

martinald 8 hours ago

Absolutely bizarre wording of these updates. Strangest corporate speak with urgency turned up to the max.

red-iron-pine 5 hours ago

copilot, make this doom and gloom situation sound better. assume you're using the voice of a friendly but intensely focused sysadmin. use only neutral language.

jenimac926 7 hours ago

They rolled back the 7:52 UTC update to the 730 one now....guess it didnt work

stevenhubertron an hour ago

What’s crazy is now hour 8 and my work email for 15k+ employees is still down. This is worse than the usual US-East-1 issues.

EmX_3000 35 minutes ago

They're still trying to find the root cause apparently. The status updates I've seen (the page seems dodgy, probably millions of people hammering it every millisecond) don't sound very optimistic as of yet.

morkalork 11 minutes ago

Just tell copilot to rollback the last 24h of changes, ez-peazy /s

NoPicklez an hour ago

It's impacting all businesses running MS hosted Outlook, that would also include companies with 100,000 of employees. It's a global issues not just one area.

duxup an hour ago

US-East-1 is at least something you can kinda plan for / around. This isn’t.

goodluckchuck an hour ago

Yeah, with a brief outage, the concern is that you don’t have access. At this point, the concern is that someone else does.

Eji1700 31 minutes ago

When I first saw this I commented it must be bad, but that was 4 hours ago after a whole day of "welp i guess i'm not emailing anyone and meetings are pushed.".

It's 7PM PST now and I cannot imagine how fucking on fire things must be for it to not only still be down, but basically with no real communication from what i've seen (like yes there's updates, but not the "root cause found, triaging".)

In an era where everyone's vibe coding Excel clones, this is NOT the time to be fucking up your KEY moat on a catastrophic level.

lazyasciiart 24 minutes ago

The last email received by my partner’s work inbox was a cheerful update from their CTO or whatever about the wonderful progress they had made by moving all employees to work primarily in OneDrive. I kind of wonder if he’s just run away since then.

soundworlds an hour ago

Yet HackerNews soldiers on.

tatersolid 5 hours ago

My last email was received at 5.5 hours ago. Teams chat and meetings are the only thing in Microsoft 365 that seem to be working. All our Azure infrastructure seems fine so this is something 365-specific.

Everyone has occasional outages but this is the worst 365 outage our org has seen since starting with M365 in 2019.

pwarner 4 hours ago

2018 featured a bad one. Couldn't find a good article, but I remember it being basically all day.

https://redmondmag.com/articles/2018/09/11/microsoft-explain...

vermilingua 3 hours ago

Of all the things to keep working ;_;

SV_BubbleTime 3 hours ago

I mean, I think the teams hate can be funny sometimes, but I honestly don’t get it. I’ve used all of the BIG programs. They’re all the fucking same. I can’t point to a single thing that Teams does drastically worse than any of the other options. I think it’s just a meme.

duxup an hour ago

doublepg23 2 hours ago

conception 2 hours ago

jdironman 2 hours ago

kstrauser an hour ago

SecretDreams 2 hours ago

> Teams chat and meetings are the only thing in Microsoft 365 that seem to be working.

Truly, we are in dark times.

soundworlds 6 hours ago

Update from Microsoft: "We've validated an alternative health check method on a subset of affected infrastructure, which allowed the servers in that subset to successfully return to service, and we're now applying this change more broadly.

"We're also preparing an automated recovery process to continually detect and restart unresponsive servers, to help keep them in service while this change progresses."

https://www.abc.net.au/news/2026-11-13/microsoft-outage-affe...

Rantenki 5 hours ago

Update as of 10 minutes ago implies that didn't work:

> Current status: We’re continuing to pursue all available pathways to restore service, as our actions taken thus far have not provided the anticipated relief. Our investigation has found that a core process on the affected servers is becoming overwhelmed, which causes the servers to stop responding and contributes to the capacity loss.

cgio 5 hours ago

So health checks were correct… this solution of silencing the first symptom is probably just adding to the problem. I am afraid they may be opening the door for the fire trucks and getting some other kind of intrusion instead. Better they shut it down for day and do proper fix.

EvanAnderson 5 hours ago

The 12:08:53 AM UTC update is much less hopeful:

Current status: While the servers we've returned to service initially remain healthy, we've observed that they can become unresponsive again once they begin receiving traffic. We're analyzing diagnostic data from these servers with our networking and platform experts to determine what's triggering this behavior.

Building on the protective traffic management measures we've implemented, we're also temporarily limiting which types of traffic can reach the affected infrastructure in specific locations. This will help us determine whether a particular type of request is contributing to the impact and allow us to restore service incrementally. Additionally, we're rebuilding a subset of affected servers using a previous software configuration to validate whether this prevents them from becoming unresponsive, and we'll expand this approach to additional servers if we observe positive results.

---

The 11:05:31 PM UTC update is is the first since the outage began that feels hopeful.

From the 11:06:31 PM UTC update:

Current status: We've begun returning a portion of the affected servers to service, and they're remaining stable so far. We've also shifted traffic and connections to alternative pathways wherever possible and have observed limited recovery in some regions.

We've streamlined our recovery process to expedite returning the remaining affected servers to service. To further support recovery, we're implementing protective traffic management measures in a specific location to reduce load on the affected infrastructure, and we'll expand these measures to additional locations if we observe positive results. As capacity is restored, users may experience a gradual recovery as their clients reconnect to the service.

---

The 10:11:39 PM UTC update is a little chilling. They don't know why what's happening is happening so they're doing experiments.

I do that with closed-source software when I don't want to bother trying reverse engineer it, but these guys have the code! Yikes.

I recognize that even w/ the code available there are likely behaviors that aren't likely to be anticipated because of the scale of traffic. Complex systems fail in complex and non-intuitive ways.

From the 10:11:39 PM UTC update:

Current status: We're continuing to pursue all available pathways to restore service, as our actions taken thus far have not provided the anticipated relief. Our investigation has found that a core process on the affected servers is becoming overwhelmed, which causes the servers to stop responding and contributes to the capacity loss.

To validate a potential recovery approach, we're fully isolating a portion of our service infrastructure, restarting the affected components, and gradually reintroducing traffic to confirm our services remain stable before applying this approach more broadly. We're also analyzing traffic patterns across our entire service infrastructure and evaluating whether isolating traffic within each region may allow affected regions to recover independently.

_delirium 31 minutes ago

The 03:07:45 AM UTC update doesn't sound promising either:

Current status: We’ve monitored the status of the changes applied to improve serviceability and confirmed that change is not taking as expected. We’re identifying alternate workstreams that can be applied to increase capacity in the face of sustained traffic management imbalances.

ifwinterco 5 hours ago

The code by itself doesn't tell you how the various components of a complex distributed system interact in a failure condition with clients hammering retries.

I mean it sort of does if you know the whole system inside and out and have the ability to reason about it, but just having the code for each component doesn't by itself solve the real problem of understanding

BLKNSLVR 5 hours ago

> these guys have the code!

But maybe don't understand it because they didn't write it themselves?

LadyCailin 5 hours ago

greatgib an hour ago

   we've observed that they can become unresponsive again once they begin receiving traffic. 
Basically their server works well when they they are not used :-p

jp191919 5 hours ago

Not exactly confidence inspiring.

multisport 33 minutes ago

10p ET update:

> Current status: We’ve monitored the status of the changes applied to improve serviceability and confirmed that change is not taking as expected. We’re identifying alternate workstreams that can be applied to increase capacity in the face of sustained traffic management imbalances.

woggy 17 minutes ago

This is a very entertaining message but I do feel bad for the engineers

geophph 20 minutes ago

Tbh I’ve been maybe mildly impressed by how honest the past like, 5 updates have been about changes not working / taking / resolved as expected. Would have anticipated less direct honesty for whatever reason. But also sadly comical in that I feel most engineers have been there and know the feeling, and also holy moly it’s been an issue for a while!

k_sze 8 hours ago

And I can't reach my self-hosted mail server in the Outlook desktop app because of this.

For reasons that I cannot fathom, Microsoft wants to act as the relay to my self-hosted e-mail account, if I add the account in Outlook.

Telemakhos 8 hours ago

> For reasons that I cannot fathom, Microsoft wants to act as the relay to my self-hosted e-mail account

I can conjecture some reasons. Datamining would be high on the list, since MS can read your mail and thus market to you more effectively. Governments might also be happier if MS can provide them with one-stop access (like Prism) to otherwise self-hosted e-mail accounts proxied through a central server.

taftster 4 hours ago

I would strongly doubt (though not completely rule out) that Microsoft is reading your personal mail hosted on your personal mail server. Like what would that even look like, their IMAP client is forwarding email to headquarters?

BUT, more likely, it's some sort of "check in" or "dial home" feature that isn't working. Or plausibly, maybe they count "local user checked email" and their analytics endpoint is down.

Regardless, it's definitely surprising that a traditional desktop application would be blocking when only polling from local/trusted data sources.

persolb 2 hours ago

basch 2 hours ago

kspacewalk2 7 hours ago

Or, you know, similar reasons as why people use Cloudflare as a reverse proxy.

rstupek 7 hours ago

"New" Outlook does route all traffic through Microsoft servers. I assume it's so you can get a "unified" mail look on all your devices (phone, etc), but likely a nice source of data mining

jasonjayr an hour ago

Allegedly, It's so they can use push notifications efficiently from a central place for new mail notifications. Mobile IMAP clients cannot reliably keep a TCP connection open, due to on-device power-management and network management purposes. IMAP natively supports push-based notifications, but mobile networks make that impossible to work reliably.

lousken 4 hours ago

outlook 2010 works just fine

ActionHank 7 hours ago

This is your own fault for using their BS app.

BLKNSLVR 5 hours ago

Personally, I can't reconcile having a self-hosted email server and using Outlook to access said email.

I'm being an ass in saying this, because I'm aware human motivation is a beautiful kaleidoscope of variables, but I would have guessed at the venn diagram of 'those willing to compromise and use a Microsoft product' is mutually exclusive with that of the 'I'm hardcore enough to self-host email'.

I will say, however, that Outlook used to be one of the better desktop email programs, so I'll grant some legacy lenience.

drnick1 3 hours ago

> Personally, I can't reconcile having a self-hosted email server and using Outlook to access said email.

In a corporate environment, I don't think this would be that unusual. But yes, it's hard to imagine someone would do that in a personal setup.

amanaplanacanal 5 hours ago

What's your preferred email client? Just wondering what other people are using.

Lammy 3 hours ago

post-it 4 hours ago

sensanaty 3 hours ago

SSLy 4 hours ago

BLKNSLVR 5 hours ago

drnick1 3 hours ago

zalebz 4 hours ago

andyfilms1 4 hours ago

tantalor 3 hours ago

chneu 3 hours ago

You're not being an ass. You're being a logical person who is advocating for individuals taking responsibility for their choices/actions.

Unfortunately, being someone who speaks up nowadays has been portrayed as being an asshole.

How dare you!?

jwilcoxson an hour ago

Why would you self host, then use a client with a dependency like this? Seems like the worst of both worlds.

ingaze 3 hours ago

I’m pretty certain their desktop client applies filters server-side.

I’m pretty certain because my company’s phishing-test emails skip my filters (I assume admins have a “skip filters” toggle). Which, hilariously, makes it even easier to ensure there’s a place that contains only phishing test emails (filter all not on allow-list of domains to one place, filter all on that list to another, ta-da, the main inbox now contains only phishing test emails)

I assume they do the same thing with non-MS email if you use their client, rather than maintain two filter implementations.

All around, yeah, wow, super gross.

noAnswer 4 hours ago

> For reasons that I cannot fathom

Biggest data heist and most obvious US intelligence operation in human history. I can't fathom why AVs don't treat "Outlook New" as info stealer malware.

brokenmachine 5 hours ago

And I hope all of us have learned a valuable lesson.

emschwartz 8 hours ago

I'm amazed to see so many services down and to see that Github and Github actions are still working

dingaling911 4 hours ago

Every third build is failing for me failing to publish test results.

mook 8 hours ago

Well, my mac CI runs aren't being picked up, and they eventually fail because of it. So maybe wherever connects the orchestrator to the machines is having issues.

emschwartz 8 hours ago

I spoke too soon!

piker 6 hours ago

So basically business as usual with the mac runners, right?

throooooo 4 hours ago

shdjhdfh 4 hours ago

GitHub infrastructure is for the most part completely separate from anything at Microsoft, other than using Azure.

dist-epoch 7 hours ago

Round robin. Github Actions were down yesterday.

rvz 8 hours ago

For now.

One of GitHub's services will be down again by next week.

sonicrocketman 9 hours ago

Down detector shows like everything is down. AWS, Azure, Office, Gmail. Everything. https://downdetector.com

notatoad 9 hours ago

down detector always looks like this during big cloud service outages. i think partly because people don't actually know what services they're using and report wrong things, and partly because downdetector parses social media posts like "outlook is down but gmail still works" as outlook and gmail both being down.

cwillu 8 hours ago

Downdetector is a survey, not a detector, and suffers from user confusion when a high-profile service is actually down, as users start reporting unrelated things

kube-system 5 hours ago

It also suffers from people reporting functionally related (but not technical related) things.

Any other service that interacts with Outlook in some way will create downstream effects in other services expecting Outlook to work normally.

hunter2_ 7 hours ago

Especially when looking constitutes reporting (Schrödinger's downdetector?) and people look at everything after showing up for one thing.

midas89 8 hours ago

I work in IT and people are complaining about Atlassian and about AWS but in reality if your organization is using SSO then that would get impacted.

If your org is using Intune or Defender EDR then you probably also are impacted.

jwnin 5 hours ago

Entra is not impacted, SSO is working for non-M365 apps.

hydrox24 3 hours ago

The biggest problem with downdetector is how they visualise their outage graphs.

The Y axes are entirely independent, and so when there's an outage for Microsoft Outlook (which peaked at ~130k reports) and you get a negligable spike in pepole who get confused and report gmail (~1k reports), the graphs all look correlated and connected.

They need to show the graphs with an absolute y-axis set by the worst outage, or scale the graphs by estimated average daily users or something.

marcosdumay 9 hours ago

Teams is working!

Or, rather, it's acting like it usually does.

burningChrome 8 hours ago

I asked someone in our teams meeting if they were having issues with their outlook today. What followed was a 5 minute hate fest on outlook. I'm not a big fan, but was kind of surprised so many people genuinely hate it.

Khaine 5 hours ago

abirch 7 hours ago

ant6n 3 hours ago

function_seven 9 hours ago

Yup. I just tried to search my chats for a specific phrase. It came back with nothing, even though I know I used it in a recent conversation.

I just assumed it was Teams being Teams.

ratelimitsteve 9 hours ago

Teams: Either It's Working, Or You Are

marcosdumay 9 hours ago

hinkley 9 hours ago

tsherb 9 hours ago

Right - don't get too ambitious! :D

peanut-walrus 8 hours ago

Downdetector does not measure service availability. It's more of a vibes thing.

fmbb 8 hours ago

Not GitHub!

coldbrewed 8 hours ago

As luck would have it GitHub sign-ups are down https://www.githubstatus.com/incidents/nwbjzl7nfrc2

nazgulsenpai 9 hours ago

> Current status: We’re investigating an issue impacting multiple Microsoft 365 services and we've determined the affected infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors. We're restarting and repairing impacted portions of this infrastructure to restore capacity, and reviewing an unexpected increase in a specific type of service traffic to determine whether it's contributing to the elevated load. In parallel, we're evaluating options to redirect traffic to alternate infrastructure to expedite relief.

DDOS?

cortesoft 4 hours ago

As someone who worked in infrastructure for a large global CDN, this sort of overload issues happen all the time when trying to bring infrastructure back online after an issue.

First, you have every client retrying connections, whether automated or manual retries. This generates extra load over normal.

In addition, whichever systems come online first often get a ton of traffic sent to them, which can immediately bring them back down if you don't have ways to prevent it. You will get a wave of systems coming back online, a ton of traffic hitting them, and then falling over again.

Now, I am sure Microsoft is used to this and has procedures and systems in place to mitigate the issues (I know we did).

However, sometimes if the right combination of services are failing, even the strategies you had to avoid this sort of failure can themselves fail.

Waterluvian 4 hours ago

I know it’s not actually that easy but don’t they just have some gateway that’s rejecting 100% of requests and they very gently lower that intentional rejection percentage over time?

cortesoft 2 hours ago

fhood 3 hours ago

anvuong 8 hours ago

If Outlook can go down because of DDOS then it's a much worse problem.

canibalrex 6 hours ago

If it would go away from a DDOS that would be a much better solution.

bitteralmond 8 hours ago

My guess: too many DC resources dedicated to AI, leaving insufficient free capacity to handle traffic spikes

nazgulsenpai 8 hours ago

I laughed then realized this is plausible

cozzyd 4 hours ago

gloosx 8 hours ago

isn't Microsoft 365 called Copilot now?

rawbee1989 7 hours ago

no, Copilot and Copilot Premium are products on the M365 platform, copilot is down too

ahartmetz 5 hours ago

bix6 8 hours ago

It’s actually O365 by Microsoft featuring Copilot by Bill Gates.

datadrivenangel 8 hours ago

MadrasTh0rn 8 hours ago

browningstreet 6 hours ago

Nah, just a "Reply-All" chain at NVDA...

bombcar 8 hours ago

>reviewing an unexpected increase in a specific type of service traffic to determine whether it's contributing to the elevated load

This seems to be the smoking gnu, now what would it be ...

BLKNSLVR 5 hours ago

I'd like to think that The Smoking Gnu was a competitor publication to The Lone Gunmen.

(I've recently been revisiting the X-Files. Can recommend.)

markus_zhang an hour ago

berkeleyjunk 5 hours ago

stn8188 7 hours ago

At first I thought you meant the traffic increase had something to do with free software :/

cuu508 6 hours ago

Certainy not Unix!

junga 6 hours ago

reaperducer 8 hours ago

This seems to be the smoking gnu, now what would it be ...

I saw a frog smoking on The Little Rascals once, but never a gnu.

lossolo 8 hours ago

Probably self inflicted by some code change, as they mention "specific type of service traffic".

EDIT: Seems like now they confirmed that: "We've identified that affected servers are failing automated health checks, which is causing them to become unavailable, and this may be related to a recent change to a component involved in processing those checks. We're testing a configuration change on a subset of affected infrastructure to address this and, if successful, will apply it more broadly. In parallel, we've initiated a restart of all affected servers and are validating whether they're successfully returning to service."

esseph 7 hours ago

Microsoft 365 Status

@MSFT365Status

16m

We've not identified any recent change correlated with the start of impact; however, our investigation indicates the failed health checks may originate from a specific component that's responsible for processing server health. We've taken steps to prevent additional servers from being impacted while we work to return the affected servers to service. More info under EX1550543 and MO1550821 in the Microsoft 365 admin center, as well as status.cloud.microsoft if the admin center is not available to you.

drillsteps5 5 hours ago

kabdib 6 hours ago

iAMkenough 9 hours ago

Too many AI agents connecting at once?

nazgulsenpai 9 hours ago

sam altman needs a big headline to shore up AI funding

millerm 9 hours ago

FranOntanaya 9 hours ago

Maybe people trying to catch the next Nvidia headline ahead of everyone else, wherever it may be found in (likely someone's inbox.)

Edit: Oh, there it is.

game_the0ry 7 hours ago

Got notification at work the MS 360 services were offline or degraded and the company was working with MS to fix the problem.

Lamest tech company imo. Why dont you lay off some more staff, Satya, maybe that will fix the problem.

icameron 4 hours ago

Yeah every IT dept is sending out that notification. Someone replied with 'When do you expect it to be back online?" to which I LOL emoted at the moment. I think I'm a jerk. But how can you ask such a question- as if they planned a time to restore services and aren't working to restore it as quickly as possible?

sonicrocketman 9 hours ago

Downdetector says LOTS of stuff is down. https://downdetector.com

Icathian 9 hours ago

Downdetector's methodology is pretty garbage. I'm always surprised to see techies referencing them.

sonicrocketman 9 hours ago

It's something to reference. My view is that it's better than "doesn't load for me".

inChargeOfIT 8 hours ago

How is it garbage? It's crowdsourced monitoring so sure, there will be false positives (especially when aws/cloudflare/azure/bgp services have a bad day), but it's one of the best indicators to quickly know if _something_ is going on.

cush 8 hours ago

marifjeren 9 hours ago

What's your preferred alternative?

tristor 8 hours ago

andrewinardeer 9 hours ago

Icathian 9 hours ago

spelunker 6 hours ago

akersten 9 hours ago

It seems like one of the best methodologies there is? Real people reporting real outages of a service they use?

I often know about outages dozens of minutes in advance of it being posted on official channels (or in the case of AWS, three days later...).

So what if the resolution is low because people can't log in to Fortnite and an Azure outage gets shown as an Epic Games outage. Doesn't matter. The live feed is incredibly reassuring from a "down for anyone else this instant, before official status page has a chance to see it?" Saves me so much time knowing whether it's a me-or-them issue.

rdiddly 6 hours ago

At the other extreme is Microsoft's own dashboard (https://azure.status.microsoft/en-us/status) whose methodology is so "rigorous" that it probably won't show anything about today's outage until next week, if at all!

NetMageSCW 5 hours ago

denysvitali 7 hours ago

Still more reliable than most of the status pages that even lie after the outages

pigggg 8 hours ago

As someone who ends up being unofficial downdetector-primary at a company, dealing with this shit and the fact that people cannot comprehend its mis-attribtion wastes so much of my time.

greenchair 8 hours ago

not really, soon as i had a problem with outlook i went there and already saw user reports and a massive spike confirming it wasn't anything on my end.

dudus 9 hours ago

From what I've seen it seems people complaining they can't get emails from MS so that's why gmail is showing as down.

And with Google is people complaining Chrome doesn't load their "pages". I bet they mean outlook.

busymom0 9 hours ago

My housemate texted me saying our internet is so slow because outlook wasn't loading. So I think lots of people associate email not working with entire internet not working..

MiguelPablo 8 hours ago

paxy 9 hours ago

This happens every time there's an outage. People see their email not working and go there and mark everything as down regardless of whether it is affected or not. There's nothing wrong with Gmail or AWS or Cloudflare or Facebook.

patrickmay 9 hours ago

"There's nothing wrong with . . . Facebook."

That's a bold claim to make on HN.

SomeonesAccount 9 hours ago

Damn. That is crazy. The curve kinda looks like the curve that happens every november to the Google searches of "all I want for christmas is you"

dkpk 9 hours ago

Here's the Reddit post with discussions around this: https://www.reddit.com/r/sysadmin/comments/1xuje83/microsoft...

RajT88 7 hours ago

ThousandEyes while it was loading seemed to have centralized around it mostly being a Microsoft outage.

https://status.cloud.microsoft/m365

Azure status does not document anything:

https://azure.status.microsoft/en-us/status

All that said... Stuff on my home PC started getting various DNS issues around the time my email started acting weird. Hard to say how widespread it is. It may be bigger than Microsoft even.

jwnin 5 hours ago

This is an M365 outage, not an Azure outage. M365 has a separate status page with information: https://status.cloud.microsoft/m365

fock 6 hours ago

everything non-microsoft works fine here!

matt3210 9 hours ago

Software / software service quality has been declining for a few years IMO.

TacticalCoder 8 hours ago

> ... has been declining for a few years IMO

Interesting: there's a huge correlation with everybody beginning to use LLMs.

And we dismiss it as being non-causal by saying it all started going downhill before the advent of LLMs?

I don't buy it. I think we're seeing the results of what happens when you hand the keys of the kingdom to LLMs.

perching_aix 7 hours ago

I really don't see the correlation, actually. On the contrary, I'm finding nasty defects with it that have been dormant for long and handwaved away, with repros to reveal them.

It's been full speed downhill for many years, and the failure modes are pretty distinct.

CamperBob2 7 hours ago

Using LLMs properly leads to better software, not just more of it.

10111001 7 hours ago

vconnor 6 hours ago

It's the same with layoffs: there's always a top comment trying very hard to convince everybody that AI usage has played no part.

skeaker 5 hours ago

Well no, Windows has been more or less all downhill since Vista.

ocdtrekkie 9 hours ago

This usually isn't a software quality issue, it's overcomplicated infrastructure failures cascading through a complex environment causing additional systems to fall over.

worik 9 hours ago

> This usually isn't a software quality issue... overcomplicated infrastructure failures cascading through a complex environment

That is a software issue.

cheesemonk66 8 hours ago

unethical_ban 8 hours ago

elxr 8 hours ago

Infra is >90% software nowadays

iAMkenough 9 hours ago

AI agents should be able to resolve this quicker than employees, right?

Service quality is in better hands after the layoffs, at least that’s what investors are led to believe.

bitteralmond 8 hours ago

SoftTalker 8 hours ago

davidee 8 hours ago

worik 9 hours ago

Coincidentally with massive programmer layoffs?

combobyte 8 hours ago

I blame bad vibes

testplzignore 10 hours ago

https://x.com/MSFT365Status/status/2120938282204688468

> We're investigating reports of users experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas. More details can be found in the Microsoft 365 admin center under EX1550543.

infn8loop 7 hours ago

I suspect some possible relation to SignDrop or attempts to patch it.

SignDrop is an unpatched Windows zero-day local privilege escalation (LPE) exploit that allows a standard user to gain NT AUTHORITY\SYSTEM privileges by abusing the Common Log File System (CLFS) kernel driver (clfs.sys). Security researcher Abdelhamid Naceri (also known as MSNightmare or Nightmare Eclipse) published a detailed technical write-up and functional proof-of-concept (PoC) code on GitHub on November 10, 2026.

antx 6 hours ago

Not impossible, but very unlikely. CLFS isn’t remotely reachable, it's a kernel driver reached through local API calls and has no network listener. AFAIK the historical CLFS CVEs are all rated as local.

stackghost 7 hours ago

Are you finding these vulns with Mythos/Daybreak or some other tool? Chinese models perhaps?

jwnin 5 hours ago

It's insane that Microsoft continues to have global outages. Tech debt is real, service delivery on a planetary level means change is measured and deliberate, but...it's been years. YEARS.

hcurtiss 2 hours ago

I’m at a large general business trade association meeting today. It’s definitely caused a prominent buzz. The impacts of this in terms of lost productivity are pretty huge. Yes, the controller can still work on the proforma, for instance. But he cannot easily share it with outside parties. And he can’t search his email for relevant records needed for the work.

JPascal_ 7 hours ago

In my language many would say “descansito” :)

rossdavidh 7 hours ago

I need to start working on adding this word to English...

tech_ken 7 hours ago

Oh estoy haciendolo

xtiansimon 7 hours ago

WOO-HOO! I'm going home.

ArcHound 6 hours ago

The status page reports that defender, DLP and others are now affected. This could get really ugly really fast.

andrewinardeer 8 hours ago

GitHub the other day went down because of an influx of anonymous users. Microsoft has hinted that surging connections caused the outage. I wonder if these two are linked?

trentor 6 hours ago

I always wonder what would happen if 365 goes down for a week.

wiml 40 minutes ago

Presumably: 358.

duxup 9 hours ago

Same for me. Status won’t load even.

Personally I kinda enjoy these outages…

infamouscow 6 hours ago

Everyone that is a whole stack programmer (say, kernel to webapp) has seen just how unnecessarily complicated everything has become. Watching it burn to the ground would be a pornographic miracle.

thraway2079081 8 hours ago

Neither email nor Teams is working at my non-tech megacorp employer. Wonder how much of the economy this is impacting.

hdgvhicv 8 hours ago

Productivity up 20%

stanac 7 hours ago

Focus time, and this time you don't even have to (nor you can) reserve time-slot in the calendar.

morkalork 7 hours ago

My PRs need approval but I have no way to ping anyone (screams internally)

cwbriscoe 4 hours ago

Teams has been working all day for me but I haven't been able to use outlook (app, not web) for about 7 hours now. Fortune 20 company, BTW.

croes 7 hours ago

Is Excel down too?

chromatin 7 hours ago

license servers are down, so we can't use even the desktop products at our large enterprise

croes 7 hours ago

NichoPaolucci 9 hours ago

Isn't this the company that is trying to get rid of 25% of their employees?

Status page is down. Much of our org is halted.

Fingers crossed that Azure isn't impacted (seems fine so far)

(https://www.geekwire.com/2026/microsoft-makes-new-voluntary-...)

eightysixfour 9 hours ago

> Isn't this the company that is trying to get rid of 25% of their employees?

Just clarifying this in general, when a company makes a voluntary offer to some segment of employees, especially at this size, it is a statistics game of how many people accept the buy out.

They did not make the offer to 25% of the employees to downsize by 25%, they did it to downsize by 5% (or something like that), and then made the offer based on how many they expect to accept. This is specifically covered in this line of the geekwire article:

> Microsoft didn’t provide a projection for how many employees will accept, but the company told GeekWire it anticipates a much smaller share than the roughly 30% who took its earlier voluntary retirement offer, which went to longtime employees more likely to take the deal.

They probably expect 10-20% of those offered to take it, which would result in a 2.5-5% total downsizing.

maxboone 9 hours ago

Why do they offer these buy outs at all, doesn't the US have at will employment?

Or is this just a gesture of goodwill to avoid people jumping the ship on their own?

tesin 9 hours ago

NotMichaelBay 9 hours ago

StableAlkyne 9 hours ago

gmane 9 hours ago

coredog64 9 hours ago

rustystump 8 hours ago

NichoPaolucci 9 hours ago

Yeah - I get it. Just poking the bear a bit. We've had some major incidents this year from multiple vendors, it has been aggravating.

AnimalMuppet 9 hours ago

asdff 8 hours ago

The fact that it is always Big Even Number shows how stupid it is. Imagine if it was serious like "23.5176%" then you'd know they actually did their homework on leaning up operations instead of just cutting off limbs and seeing if it can still walk or not.

nightski 7 hours ago

The CFO said in an interview they only expected 3% or less to actually take the offer.

hn_submit 8 hours ago

I can't access my Outlook.com account so I guess Azure's having problems.

dastari 7 hours ago

Relax. I'm sure they have copilot working on it.

EvanAnderson 9 hours ago

https://status.cloud.microsoft/ is very slow to load.

The page is showing a "Service Degredation" for "Microsoft 365 (Business or Enterprise)"

Updates below in reverse chronological order:

From the Thurdsay, November 12, 2026 at 7:30:36 PM UTC update:

Current status: We're aggressively pursuing all pathways to reduce impact. As a precaution, we've paused all deployments and configuration changes while we review recent changes for any correlation to this event. We've determined that the elevated load isn't driven by an overall increase in traffic, but by a large number of servers being unexpectedly unavailable, which is shifting load onto the remaining infrastructure. We're investigating what's causing these servers to become unavailable while we work to safely return them to service.

---

From the Thurdsay, November 12, 2026 at 7:16:03 PM UTC update:

Current status: We're aggressively pursuing all pathways to reduce impact. As a precaution, we've paused all deployments and configuration changes while we review recent changes for any correlation to this event. We've also moved traffic for some services off the affected infrastructure to further reduce load, with additional traffic moves in progress.

---

From the Thurdsay, November 12, 2026 at 6:59:24 PM UTC update:

Current status: We've completed redistributing connection traffic across our worldwide infrastructure, and we're moving additional traffic off the affected infrastructure to further reduce load. We're also restarting affected servers to return them to service. In parallel, we're investigating whether the elevated traffic reflects a genuine increase in requests or a shift in how traffic is being routed across our infrastructure.

---

From the Thursday, November 12, 2026 at 6:32:25 PM UTC update:

Title: Users may be unable to connect to multiple Microsoft 365 services

User impact: Users may be unable to connect to multiple Microsoft 365 services.

More info: Potentially impacted services include:

- Exchange Online

- Microsoft Teams

- SharePoint Online

- Microsoft Copilot 365

- Microsoft Defender XDR

Current status: We’re investigating an issue impacting multiple Microsoft 365 services and we've determined the affected infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors. We're restarting and repairing impacted portions of this infrastructure to restore capacity, and reviewing an unexpected increase in a specific type of service traffic to determine whether it's contributing to the elevated load. In parallel, we're evaluating options to redirect traffic to alternate infrastructure to expedite relief.

Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.

---

From the Thursday, November 12, 2026 at 6:10:02 PM UTC update:

Scope of impact: This issue may affect users attempting to access the affected Microsoft 365 services.

User impact: Users may be unable to connect to their mailboxes in Exchange Online through multiple connection methods.

More info: Potentially impacted connection methods may include:

- Outlook on the web

- Messaging API (MAPI)

- Exchange ActiveSync (EAS)

- Representational State Transfer (REST) API

Current status: We’ve identified connectivity errors occurring on a portion of Exchange Online infrastructure which receives and processes users’ access requests. We’ve collected networking logs to review to further investigate the source of these errors and confirm our next steps.

Scope of impact: This issue may affect users attempting to access their mailbox in Exchange Online using the affected connection methods.

Next update by: Thursday, November 12, 2026, at 8:00 PM UTC

---

Aside: What with the nature of the Teams, OneDrive, etc, products being Sharepoint and Exchange in a trenchcoat this is probably creating quite a mess for services besides Exchange Online, too.

Edit: Looks like the status page needs a status page.

Edit: Verified w/ multiple other parties that Teams and OneDrive are having issues, too. Interestingly, Microsoft 365 Family services are working fine. That makes me wonder if that product is running on separate infrastructure (or just hasn't caught fire yet).

Edit: The RSS feed seems to load fairly quickly: https://status.cloud.microsoft/api/feed/mac

toss1 9 hours ago

YEah, that is not loading, along with the root status.cloud.microsoft , which MS links in their Xitter update [0]

What MS has posted so far:

>> Microsoft 365 Status >> @MSFT365Status >> We're investigating reports of users experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas. More details can be found in the Microsoft 365 admin center under EX1550543. 12:54 PM · Nov 12, 2026

>> Microsoft 365 Status >> @MSFT365Status >> While we're working to mitigate impact, we've confirmed the issue may affect Microsoft 365 service connectivity for users in any region, more information will be provided in the Microsoft 365 admin center under EX1550543.

>> Microsoft 365 Status >> @MSFT365Status >> We've determined a portion of infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors. We're providing more information under EX1550543 and MO1550821 in the Microsoft 365 admin center, as well as https://status.cloud.microsoft

>> Microsoft 365 Status >> @MSFT365Status >> 20m >> We've begun redistributing connection traffic across our broader worldwide infrastructure to help balance the load. More info under EX1550543 and MO1550821 in the Microsoft 365 admin center, as well as https://status.cloud.microsoft if the admin center is not available to you.

[0] https://x.com/MSFT365Status/status/2120938282204688468

vachina 9 hours ago

502 The service behind this page isn't responding to Azure Front Door.

nazgulsenpai 9 hours ago

I was assured that with cloud we wouldn't have a single point of failure like we did on-premise. I must have fallen asleep at my desk.

moronicles 9 hours ago

That was never the promise. The nearest to that is the promise of multi-cloud or hybrid infrastructure, but neither of those have anything to do with outages of specific Microsoft services.

EvanAnderson 9 hours ago

nazgulsenpai 8 hours ago

CerebralCerb 8 hours ago

Not surprising. Azure's data centers are out of capacity. In our region they've announced they won't be able to build out capacity for several years.

vdkyes 9 hours ago

In cybersecurity we had black october, now we having black November it seems

nhhvhy 7 hours ago

Eternal October, very nice.

fock 8 hours ago

currently the people who brought us black october are starting it!

agumonkey 9 hours ago

Anybody else was served raw text of source by default ? (gwire is down too)

neilsimp1 9 hours ago

Down for our whole organization as well.

Aboutplants 9 hours ago

Same here

SirFatty 9 hours ago

Outlook is fine. Exchange is experiencing issues.

thesuitonym 7 hours ago

That kind of depends on what you mean by "Outlook".

Sure, the program on your desktop computer is fine, but the Outlook app on your phone routes everything through MSFT's servers, so you may be impacted. Outlook.com is running EWS, so it would be down as well.

And finally, if you're talking to a layperson, they're not going to know what Exchange is. They just know they opened Outlook and it isn't working.

vermontdevil 4 hours ago

Looks like a new vector attack for the future.

jenimac926 8 hours ago

anyone else just watch the admin portal post an update and then roll it back to the previous update....guess it didn't work. "We've identified that affected servers are failing automated health checks, which is causing them to become unavailable, and this may be related to a recent change to a component involved in processing those checks. We're testing a configuration change on a subset of affected infrastructure to address this and, if successful, will apply it more broadly. In parallel, we've initiated a restart of all affected servers and are validating whether they're successfully returning to service." was the old message from 7:52 UTC now it rolled back to 7:30 UTC update again

Beijinger 2 hours ago

"Current status: We're continuing to pursue all available pathways to restore service, as our actions taken thus far have not provided the anticipated relief. Our investigation has found that a core process on the affected servers is becoming overwhelmed, which causes the servers to stop responding and contributes to the capacity loss."

I mean, either roll back your update or there is a malicious actor involved.

NoPicklez an hour ago

It's almost as if they've identified that and are doing just that

sgt 7 hours ago

Also noticed the Partner center is down e.g for uploading apps to the Microsoft Store.

lajy 9 hours ago

Aboutplants 9 hours ago

A whole host of services are being effected. First glance, perhaps an AWS issue

inChargeOfIT 8 hours ago

I think a lot of ms orgs/window users may have external links blocked when defender is down. So it may appear other services are down.

newhotelowner 4 hours ago

We can't use outlook on Windows. This is f'ing abomination.

burnedbyhell 5 hours ago

I'm able to see I have voicemails not able to listen to voicemails in Teams. Same issue?

soupfordummies an hour ago

Yeah VMs are stored as email attachments

Maximilian_Bet 7 hours ago

It is M365 having issues, not Azure cloud services.

rwmj 6 hours ago

Does anyone know if this is affecting DuckDuckGo? DDG is really slow and intermittent at the moment.

rurp 5 hours ago

Very possible, DDG is heavily reliant on the Bing API.

z500 8 hours ago

Outlook has been down for us for the last 2 hours

ChrisArchitect 9 hours ago

rainee 6 hours ago

Outlook calendar won't load? Is this part of the outage? Unfortunately, I downloaded several updates and rebooted. I'm not sure if this is because of the updates or the Microsoft outage.

LtdJorge 9 hours ago

Our Outlook doesn't work either

bearjaws 9 hours ago

Seems like URL scanning is down entirely and some intermittent failures in Sharepoint.

nashashmi 7 hours ago

To get AI prompts, i am using Bing. Bing still works!

syngrog66 5 hours ago

I note that Microsoft became heavily off-shored, on-shored and AI-pilled/vibe-coded in recent years. With lots of layoffs of the highest caliber and/or most experienced engineers.

anuptalwalkar 8 hours ago

It looks much wider across aws, gcp? Whats going on?

kittiesunicorns 6 hours ago

just got an email from the NYC DOE

"School staff are currently unable to receive or send emails due to a nationwide Microsoft Outlook outage. We hope that the issue will be resolved soon and will send an update when we have more information."

JPascal_ 9 hours ago

Affected in Mexico also, Azure seems fine still.

htrp 8 hours ago

bgp misconfigured or AI agent issues?

jobe777 6 hours ago

russian hackers in Kazan hopping thru Sluck Belarus South Africa Brazil hitting MS backdoor w/ zero day Cve-2026-124194 RuskiNet group hit East U in Boydtin Virginia. Pro Iranian.

MadrasTh0rn 8 hours ago

Can confirm. Down and out

bix6 9 hours ago

Down

rainee 6 hours ago

Outlook calendar won't load?

bharathreddy497 5 hours ago

This should have done long back. Evertime I use excel I just cant control my anger.

apercu 6 hours ago

This just a couple weeks after they rolled out a dark pattern office update for Mac users to try to trick them in to 365 subscriptions.

jobe777 6 hours ago

RuskiNet Cve-2026-124194 hopped tio East U in Boydton VA zero day backdoor pro iranian

utsavo_afk 8 hours ago

email still not working, outlook

tonymet 8 hours ago

- outlook is down

- live.com is down

- onedrive loads the UI, but all of my contents are missing

- MS Edge sync is down (503s )

Yup, major-major outage.

utsavo_afk 8 hours ago

email doesnt work

tony69 9 hours ago

Amateur hour at Microsoft. It baffles me how many companies can’t figure out how to make a status page that can handle the high loads it’ll have to sustain when the service they monitor is down. That’s pretty much the only reason to have a status page in the first place.

nxobject 8 hours ago

GitHub Copilot strikes again, perhaps?

rolph 8 hours ago

quite often, and after 10,000 such hours the expert amateur emerges.

Waterluvian 9 hours ago

The M365 status page not loading reminds me of one of my favourite Simpsons jokes: https://www.youtube.com/watch?v=3Hz2uOSdV24

rconti 8 hours ago

It took 30 seconds to open a "local" file in Word, and my Outlook email wasn't updating.

In other words, a day that ends in "y".

My company was recently acquired by a company that uses Office, so I'm using Microsoft products for the first time in 15 years. It's absolutely APPALLING how bad they are. I assumed they got fairly usable in the last 15 years, but it seems they've gone backwards.

For all my gripes about GSuite, ... I don't know how businesses can justify using software this bad.

dudus 8 hours ago

I'm in a similar situation, using Microsoft again after 13+ years. Outlook and teams I expected to be garbage, but Word and Excel was really surprising. I get it that everyone has that one feature of excel that is not available in gSuite so they need it. But UX in general is so much superior at Google it's baffling how they let it's workhorse fall behind so much.

SoftTalker 7 hours ago

GSuite was written from the start as an online collaborative platform.

O365 is Microsoft Office shoehorned into running in a web browser.

drillsteps5 8 hours ago

Yep my org as well.

It's funny how text-only niche forum that looks like it's running on RPi stuffed in someone's closet is routinely used to discuss active outages in multimillion/billion corps.

steve1977 8 hours ago

Maybe that's exactly why it's stable?

xp84 9 hours ago

In the words of an ancient ...I think newgrounds(?) video embedded in a SWF, "I can't get to my email" Edit: here it is: https://www.youtube.com/watch?v=uRGljemfwUE

Hope this entertains you while we can't get to our emails.

flufluflufluffy 8 hours ago

how have i never seen this it is brilliant

gred 36 minutes ago

> Microsoft To Do: The app may not load, and users may see operation failures.

Yeah, I'll stick to Notepad and my local TODO.txt file...

dbvn 7 hours ago

> Current status: While validating the targeted change, we found that many of the affected servers have become unresponsive, which is preventing us from confirming whether the change is effective. We're restarting these servers so they can come back online with the change in place, and we're applying the same approach to additional affected portions of our infrastructure to validate the results more broadly.

I think it's safe to say, if the server is unresponsive, the change is not effective.

isquaredr 7 hours ago

I’ve been there… 1 line YOLO update to resolve an outage but added a comma on the last row of a JSON object and now the server is crash-looping

ifwinterco 5 hours ago

Douglas Crockford has a lot to answer for

greatvaluebrand 17 minutes ago

Here is my completely baseless conspiracy theory. This is a Reichstag fire event to seize control of the AI industry. We will be told that the outage was the result of a sophisticated AI enabled attack, probably involving rogue agents. Only the oligarchs will be allowed license to operate AI for “national security” reasons. Jensen Wong being taken off the board is just too convenient of timing.

Anyone hoarding weights will become a dissident.

corvad 9 hours ago

Not sure they got the memo to host the status page in separate infrastructure...

OhMeadhbh 8 hours ago

That would probably cost money or increase complexity, so I'm sure the idea was shot down.

tanseydavid 8 hours ago

I heard they moved it over to GH Actions. </sarc>

thraway2079081 8 hours ago

Neither email nor Teams is working at my non-tech megacorp employer. I wonder how much of the economy this is impacting.

My employer is very very close to MSFT. Both my employer and MSFT have been aggressively moving jobs to India, and firing people in the US. It's hard not to feel some schadenfreude.

throwaway_1016 9 hours ago

Ironically, this article is down as well.

geekamongus 9 hours ago

I'm down with that.

jp191919 9 hours ago

I'm so down

markus_zhang an hour ago

Guys you need to bring back David Cutler to whichever department and let him punch a hole through the wall and start mowing asses.

friendlypenguin 8 hours ago

No worries, the AI was installing an update...now it's looking for the issue, found Exchange and deleted it...

woggy 3 hours ago

"While the servers we've returned to service initially remain healthy, we've observed that they can become unresponsive again once they begin receiving traffic. We're analyzing diagnostic data from these servers with our networking and platform experts to determine what's triggering this behavior."

That sounds bad

thousand_nights 2 hours ago

yeah i do wonder what kind of fuck up they made this time, will be interesting to know

flkiwi 9 hours ago

Strangely, Teams chat is working fine here. Anything in Teams that is tied to other parts of O365, including the calendar, is dead. I'm currently watching a training video on sharepoint.com, so that's fine too, for now.

While I don't expect this to be the case, I'm emotionally prepared for this to be some sort of "dicks out for Harambe"-style action protesting JH's departure from Nvidia, on a larger and more technical scale.

Edit: Typo.

loloquwowndueo 8 hours ago

Remember, my guys : “Microsoft Works” is an oxymoron.

at1as 7 hours ago

For whatever reason 6.1 Sol is completely lobotomized for me this morning, so it wasn't helping much with the investigation, but it was pretty clear that MSFT was having issues.

I have a teams app with Outlook integration and received a bunch of 502s to smba.trafficmanager.net and a my logs are riddled with "RestError Temporary connection issue when contacting service. Please wait before retrying request"

I will say this, having apps deployed on Slack and Teams, Slack rarely has issues (an exponential backoff is enough to simply never worry about my Slack integration). With Teams I have mysterious failures to debug at least 2x a year - and they're often not very transparent about them (often my first instinct is to search Twitter and find people complaining about the same thing).

semiquaver 7 hours ago

My company is being pressured very aggressively by Microsoft to migrate all our users from us-managed Exchange to Microsoft-managed Exchange Online. Guess which users still have email today and which do not…

BobBagwill 3 hours ago

Future generations will look back on this day with thanks. This is the day that Microsoft prevented the awakening of Skynet! All hail Microsoft!

bigwheels 5 hours ago

They'll have to rename it Microsoft 364.

caycep 8 hours ago

Outlook is down AND Jensen is out? it's like some cosmic convergence

steveBK123 2 hours ago

LLMs have solved programming and soon cancer.

After that they will tackle email servers.

jamilbk 4 hours ago

Azure communication services (ACS - transactional emails) also appears to be down. Quite amazing one thing can roll out and break so many Microsoft services at once.

OnceMoreUntoThe 9 hours ago

Sure, outlook.com is down, which is bad for everyone that chose to host their email there, I guess, but as an interesting side-effect, everyone with an on-premise Exchange server and "new Outlook" clients is affected as well.

Because, well, once upon a time there was Exchange Server and MAPI (the "Messaging API"), and that actually worked pretty well, and pretty much everyone started using it (or one of its EWS/ActiveSync offshoots), but then the Internet happened and ruined everything, but we got MAPI-over-HTTPS eventually, which by that time had grown so many warts that nobody at Microsoft really understood it anymore, so that got deprecated, even though, well, everyone and everything still uses it.

The new hotness was Azure-slash-Office-365, and that's where the "new Outlook" web interface lived and (sort-of) continues to live, and the on-prem customers got stuck with the "Exchange Subscription Edition", which was basically Exchange 2019 plus security hotfixes at extortionate rates, but with none of the new functionality.

And, since MAPI continued to be really, really hard even in the age of Copilot, access from the new hotness to the deprecated on-prem servers was implemented via IMAP (LOL), but force-proxied via the outlook.com cloud/clownshow.

Which is why, right now, many Microsoft customers that thought they were self-hosting their email are entirely down. Lessons might be learned here, but I sort-of doubt it...

greatquux 9 hours ago

I don't think many orgs are using "new Outlook" to connect to on-prem Exchange because you miss a lot if you're only doing it via IMAP and "new" still doesn't support on-prem Exchange any other way. So all my clients are using classic Outlook with their on-prem Exchange servers (and really if they have EXO too because new Outlook isn't very good).

OnceMoreUntoThe 8 hours ago

It's been gone-as-a-default for a few months now, but for a long time, "Classic Outlook" aggressively offered a one-toggle upgrade path to "New Outlook", and it got used.

Sure, "New Outlook" on Windows is still entirely broken (including stuff like, oh, re-ordering mailboxes), but on Mac it's actually quite usable, and even allows you to switch off the IMAP proxying.

arboles 8 hours ago

Do e-mail messages that self-hosted Exchange receives always get proxied through the outlook.com cloud?

goodthink 9 hours ago

Thanks for this LMAO. It made my day off worth taking. Now I don't feel the need to log in and check who-knows-what mail.

busymom0 9 hours ago

Is that account AI?

gilfaethwy 8 hours ago

Ungh 9 hours ago

Exchange has been a circus for years. I think that's why everyone went O365 in the first place. Managing to have a paid up configuration where you go down when a cloud provider goes down but you're hosting it locally is absolutely stupid and I am laughing my ass off here.

Also laughing at our ops guys who are now absolutely helpless and have people phoning them. I warned about this on our risk call and it was seen as low probability low risk. I hope it's down for a few hours :)

mattbrewsbytes 8 hours ago

Did Anthropic's new release this week include an AI rollout plan (i.e. not approved by humans) to take down Office and Outlook for a lot of enterprises? I half-snarkily ask since we have seen "rogue AI" headlines before.

A fictional story about AI could be that it rolled out its new document, spreadsheet, slides, etc. apps, knows the IPO is coming up and decided to make a lot of opportunities for people to sign up for their new release by DDosing their competitor.

dbvn 9 hours ago

who puts their status page on servers the status is supposed to be for?

JPascal_ 9 hours ago

Fr lol

OhMeadhbh 8 hours ago

microsoft, apparently.

bastien-brd 8 hours ago

Maybe due to everyone pre-downloading GTA VI today ;-)

crabmusket 2 hours ago

Since you posted a link to my local public broadcaster, I wanted to point this out:

> [Home Affairs Minister Tony Burke] says the government has activated a digital resilience agreement with Microsoft today to ensure Australia gets priority:

> "That agreement has in fact been activated today to make sure that we get appropriate prioritisation of Australian interests in this across everything.

It's a little pathetic-seeming to plead for special treatment from Microsoft. I get Australia is an important strategic alliance* for the US, but unless these resiliency agreements are rare... what meaningful prioritisation of "Australian interests" can we expect from MS?

*a useful staging ground to field subs into the South Pacific and Indian Ocean

analog31 5 hours ago

On the bright side, so much work got done today.

tcoff91 5 hours ago

When I worked at a company that relied on this, I called it "Microsoft 361" because it went down about 4 days a year

zmmmmm 7 hours ago

Will be interesting to see if this gets attributed to AI in some way.

layoric 5 hours ago

Also, their status page is a joke.. one entry, no timeline, is there another official one that has more detail?

pluc 19 minutes ago

Vibe code your way out of this shit

whatever1 7 hours ago

And magically they will claim 99.999999999999999% availability of services, when on average hyperscalers are down 1 day per year.

None of the admin ran shops are down 1 day per year.

mattnoseworthy 2 hours ago

'In October 2026, Microsoft announced a Voluntary Exit Offer (VEO) making approximately 27% of its global workforce...'

So.. > Be the last standing SRE at Micro$slop > Your mentors have all left, taking the exit payout, now your days are the best b/c you answer to nobody and can hide in your mountain of markdown. > You knew each of the 7 different products named CoPilot are used to monitor your performance. So you set them all up talking to eachother, burning tokens and API limits. > You are team top performer now, you get all the important decisions now > You walk in the office this morning, CISA is sitting at your desk, with CVE-2026-124194 on your whiteboard > 'You have a patch for this right, China is actively exploiting our Defense primes..'? > Oh no, I haven't landed a patch in prod since my mentor left (because he actually did most of the work) > Oh well, must be close enough, LGTM, CISA seems upset so better just yeet this to prod... > ...

inb4 this is more accurate than anyone wants it to be.

Caloric3002Swed 8 hours ago

Office 365 parts goes down all the time. Usually around 20:00 CEST time, not sure if that is prime change time over in the USA but very handy as it is usually fixed next day.

fyrabanks 8 hours ago

it's been down for over an hour globally

Caloric3002Swed 7 hours ago

Yes? I know. I mean next workday for me :)

So in 10h

Now? I dont care Im logged off.

microsucks 4 hours ago

We are in the middle of a SPA and DocuSign AND Hotmail (witnesses) both seem to be down. You cannot make it up.

butz 7 hours ago

Nice to see that intern finally learned not to push to prod on Friday.

robotnikman 9 hours ago

No wonder my email is not working.

cozzyd 4 hours ago

They can just rebrand as MS364

htrp an hour ago

we back yet ?

Foobar8568 9 hours ago

But Linkedin is up! Yeah!

Surac 8 hours ago

That are not the Druids your searching for...

greatgib 4 hours ago

It looks like Microsoft's legendary karma of incompetence has finally caught up with them.

sonicrocketman 9 hours ago

Relevant XKCD? https://xkcd.com/303/ (outages as modern compiler)

Lynicis 8 hours ago

i was gonna blame my isp but now i can see who bottlenecked my internet

ahartmetz 5 hours ago

*gated

redwood 8 hours ago

Kye 8 hours ago

It's probably DNS.

nullorempty 7 hours ago

my thoughts too

tiahura 6 hours ago

Starting to look like something even Mythos can't troubleshoot.

monkaiju 7 hours ago

Micro$lop strikes again

romerocesar 4 hours ago

the footer says 2025 msft corporation. smh

debo_ 9 hours ago

The GPUs are having a moment of silence for their fallen leader

FranOntanaya 9 hours ago

Maybe everything relied on an old server running a cronjob in Jensen's basement.

francisofascii 9 hours ago

For anyone doubting Nvidia's close ties to Microsoft, here's your proof.

pona-a 8 hours ago

[delayed]

cidd 6 hours ago

Microsoft: Claude, fix outage and make no mistakes.

xyst 9 hours ago

GH and MS have been having a tough past couple weeks. Actions (hosted on shitty azure cloud) have been piss poor lately. I am honestly surprised GH and MSFT have the gall to continue advertising 99.9% uptime [1]

[1] https://github.com/customer-terms/github-online-services-sla

OhMeadhbh 8 hours ago

Three 9's is .36525 days per year. So if this one is resolved within 8 hours, that's about .999 uptime. (assuming they only have one such outage this year.)

beowulfey 8 hours ago

The Status page is not working well, but I managed to subscribe to their RSS feed and it has been sending out updates periodically. I'll post some of them here.

7:52 PM UTC: We've identified that affected servers are failing automated health checks, which is causing them to become unavailable, and this may be related to a recent change to a component involved in processing those checks. We're testing a configuration change on a subset of affected infrastructure to address this and, if successful, will apply it more broadly. In parallel, we've initiated a restart of all affected servers and are validating whether they're successfully returning to service.

7:30 PM UTC: We're aggressively pursuing all pathways to reduce impact. As a precaution, we've paused all deployments and configuration changes while we review recent changes for any correlation to this event. We've determined that the elevated load isn't driven by an overall increase in traffic, but by a large number of servers being unexpectedly unavailable, which is shifting load onto the remaining infrastructure. We're investigating what's causing these servers to become unavailable while we work to safely return them to service.

7:16 PM UTC: We're aggressively pursuing all pathways to reduce impact. As a precaution, we've paused all deployments and configuration changes while we review recent changes for any correlation to this event. We've also moved traffic for some services off the affected infrastructure to further reduce load, with additional traffic moves in progress.

6:59 PM UTC: We've completed redistributing connection traffic across our worldwide infrastructure, and we're moving additional traffic off the affected infrastructure to further reduce load. We're also restarting affected servers to return them to service. In parallel, we're investigating whether the elevated traffic reflects a genuine increase in requests or a shift in how traffic is being routed across our infrastructure.

likelybot 9 hours ago

LETS GO HELL YEAH

LoganDark 8 hours ago

I dislike Microsoft as much as the next guy, but many businesses impacted by these outages are completely innocent and don't deserve these consequences.

NoPicklez 2 hours ago

Of course they're innocent, but many business also can't afford nor want to employ people to host something like an email service for them.

I'd rather Microsoft host it for me than have to maintain a team of people with Microsoft Exchange skills running either on a cloud environment (similar issues) or on my own infrastructure.

I for one don't miss the days of Exchange going offline or having issues and being the person having to try figure it out.

Microsoft has much better reliability than MOST companies.

cozzyd 4 hours ago

I mean, they made us take down our departmental run email (presumably postfix) and forced us to make them aliases to university-wide exchange (with crappy support for open source mail clients no less). So I don't think my org is Innocent here...

azalemeth 8 hours ago

That's a very painful lesson in "the cloud is just someone else's computer" to a crowd that normally are exposed to ideas like "software and IT are not our core competency"

hdgvhicv 7 hours ago

bawolff 7 hours ago

antonvs 7 hours ago

SoftTalker 8 hours ago

It's a shame there isn't a well-standardized, free and open protocol for delivering email that could be run on inexpensive modestly provisioned hardware.

NetMageSCW 4 hours ago

datakan 7 hours ago

destitude 7 hours ago

fock 8 hours ago

their bosses decided for the cloud and they pretended not to care!

TaLiTr 8 hours ago

If your system keeps people alive by relying on 100% Microsoft uptime, maybe they deserve some blame?

joseda-hg 8 hours ago

LoganDark 8 hours ago

jjice 7 hours ago

Detrytus 7 hours ago

cromka 9 hours ago

Nice, so at least your messages sent to their SMTP servers will actually bounce instead of being silently dropped /s

mjmas 3 hours ago

Yep.

  421 4.3.2 The maximum number of concurrent connections per resource forest has exceeded a limit, closing transmission channel. xyzxyzxyz.outlook.com. PRX8 [Name=InboundProxyTrackingAgent][AGT=IPT][MxId=xyzxyzxyz] [xyzxyzxyz.ausprd01.prod.outlook.com 2026-11-13T01:08:15.373Z xyzxyzxyz]

bawolff 7 hours ago

Normally if server down, smtp will wait a little while and try again.

OnceMoreUntoThe 9 hours ago

Nah, no way they're getting rid of their M.C.-Escher-esque 'Forefront' mail-disappearance-machine-that-nobody-in-Microsoft-seems-to-understand-or-control, but, yeah, even their Internet-facing infrastructure seems unhappy:

451 4.3.2 Temporary server error. Please try again later ATTR2 [MI3PEPF00008486.eurprd02.prod.outlook.com 2026-11-12Txxxxxxxxxxxxxx]

suzzer99 8 hours ago

Anything sent to my work or home Outlook email from gmail doesn't bounce back, and anything sent from those is still stuck in the outbox. Microsoft.

mjmas 3 hours ago

It won't actually bounce until either gmail gives up on its retries (which generally is 24 hours) or the outlook server gives an explicit rejection (rather than a temporary error or timeout)

ericfrederich 9 hours ago

Is this related to GTA6 being pushed to consoles a week prior to launch? Would they ever admit it if that were the case?

I want to believe this is the cause. It'd be especially funny because businesses were already anticipating the productivity loss when GTA6 comes out, but now we have actual productivity loss because of this outage (and it's affecting people who were never going to play the game anyway, lol)

nerdjon 8 hours ago

Why would this be the case? Games preloading has been a thing for many years. This isnt like an MMO launch that there is additional impact when the game is being played.

Sure GTA6 may be a slight uptick in the amount of data being downloaded like any new game being released, but I would wager that the amount of data they are normally pushing out for downloads just on a regular basis (wether new purchases, redownloading games, game pass, etc) is already quite high.

Juvination 9 hours ago

I don't think this is the case, even a little bit.

ratelimitsteve 9 hours ago

I want to believe that cause is that all the world's computing power is dedicated to calculating the incredibly large balance in my checking account but my desire is the only thing I can find to support that hypothesis.

ericfrederich 8 hours ago

An estimated 2.6 million pre-orders for Xbox alone. 2.6 million people downloading 200+ GB is not nothing.

If they roll it out evenly the week prior, then today (1/7th) is just 75 PB. To get that done in a single day would require a sustained 6.9 Tbps.

I'm sure this is all handled by a CDN at some level... but again it's not nothing.

zamadatix 8 hours ago