Hacker News new | past | comments | ask | show | jobs | submit

Service degradation on Microsoft 365

https://status.cloud.microsoft/
loading story #50473305
loading story #50475605
loading story #50474517
loading story #50473368
loading story #50473043
> 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?

loading story #50475923
loading story #50473168
loading story #50472963
loading story #50473345
loading story #50472800
loading story #50475048
loading story #50473075
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."

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.

Currently (17:22EST):

> Previous 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.

If failures started at some point in time then something must have changed just prior to that. If no changes in traffic were detected (no DDOS) then it must have been a change, be it code or config. Duuuh.

loading story #50474484
loading story #50472326
loading story #50472204
loading story #50471863
loading story #50473964
loading story #50471900
Downdetector says LOTS of stuff is down. https://downdetector.com
Downdetector's methodology is pretty garbage. I'm always surprised to see techies referencing them.
loading story #50472012
loading story #50471930
loading story #50475429
loading story #50472063
loading story #50474173
loading story #50475426
loading story #50471685
loading story #50473850
loading story #50476034
loading story #50473666
loading story #50474356
loading story #50473280
loading story #50474933
loading story #50473143
loading story #50475638
loading story #50471785
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-...)

> 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.

loading story #50472425
loading story #50472141
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.
Hmm. More than normal?

And everybody has spent a year letting AI write code. Correlation is not causation, but I wonder...

The speed of change has accelerated drastically at some organizations, so even if quality stayed the same, the number of outages would increase because of the # of changes has condensed to happen over much shorter time frames.
loading story #50472781
loading story #50473712
loading story #50473057
loading story #50474038
loading story #50473285
loading story #50471690
loading story #50471994
loading story #50474489
loading story #50471695
loading story #50473431
loading story #50472561
loading story #50473825
loading story #50474745
loading story #50474255
loading story #50473497
loading story #50471710
loading story #50474787
loading story #50474790
loading story #50472306
loading story #50473477
loading story #50473722
loading story #50472284
loading story #50475679
loading story #50473734
loading story #50474500
loading story #50471845
loading story #50471987
loading story #50473241
loading story #50473484
loading story #50472341
loading story #50475223
loading story #50474755
loading story #50473166
loading story #50474823
loading story #50474579
loading story #50472652
loading story #50471700
loading story #50472964
loading story #50474195
loading story #50472558
loading story #50473414
loading story #50472117
loading story #50471837
loading story #50474118
loading story #50475646
loading story #50475660
loading story #50475589
loading story #50472520
loading story #50474164
loading story #50472745
loading story #50473194
loading story #50472884
loading story #50475846
loading story #50475855
loading story #50472903
who puts their status page on servers the status is supposed to be for?
loading story #50472841
loading story #50474292
loading story #50474407
loading story #50475532
loading story #50472137
loading story #50473113
loading story #50473217
loading story #50473646
loading story #50472077
loading story #50472377
loading story #50472702
loading story #50474988
loading story #50473270
loading story #50473073
loading story #50471836
loading story #50471756
loading story #50473434
loading story #50473728
loading story #50473263
loading story #50472320
loading story #50472810
loading story #50472019
loading story #50474544
loading story #50472057
loading story #50473433
loading story #50472657
loading story #50473281
loading story #50472667
loading story #50473300
loading story #50472060
loading story #50472296
loading story #50472691
loading story #50472210
loading story #50472656