Starting at approximately 16:00 UTC, we began experiencing Azure Front Door issues resulting in a loss of availability of some services. We suspect that an inadvertent configuration change as the trigger event for this issue. We are taking two concurrent actions where we are blocking all changes to the AFD services and at the same time rolling back to our last known good state.

We have failed the portal away from Azure Front Door (AFD) to mitigate the portal access issues. Customers should be able to access the Azure management portal directly.

We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update.

This message was last updated at 17:17 UTC on 29 October 2025

They quickly updated the message to REMOVE the link. Comical at this point.

We already had to do it for large files served from Blob Storage since they would cap out at 2MB/s when not in cache of the nearest PoP. If you’ve ever experienced slow Windows Store or Xbox downloads it’s probably the same problem.

I had a support ticket open for months about this and in the end the agent said “this is to be expected and we don’t plan on doing anything about it”.

We’ve moved to Cloudflare and not only is the performance great, but it costs less.

Only thing I need to move off Front Door is a static website for our docs served from Blob Storage, this incident will make us do it sooner rather than later.

The root zone and www. do not: https://dnschecker.org/#A/microsoft.com (all resolvers return records)

And querying https://www.microsoft.com/ results in HTTP 200 on the root document, but the page elements return errors (a 504 on the .css/.js documents, a 404 on some fonts, Name Not Resolved on scripts.clarity.ms, Connection Timed Out on wcpstatic.microsoft.com and mem.gfx.ms). That many different kinds of errors is actually kind of impressive.

I'm gonna say this was a networking/routing issue. The CDN stayed up, but everything else non-CDN became unroutable, and different requests traveled through different paths/services, but each eventually hit the bad network path, and that's what created all the different responses. Could also have been a bad deploy or a service stopped running and there's different things trying to access that service in different ways, leading to the weird responses... but that wouldn't explain the failed DNS propagation.

I wonder if this is microsoft "learning" to "prevent" such an issue and instead triggered it...

"One often meets his destiny on the path he takes to avoid it" -- Master Oogway

Moving a website quickly is never fun.

- on a US tenant I am unable to access login.microsoftonline.com and the login flow stalls on any SSO authentication attempt.

- on a European tenant, probably germany-west, I am able to login and access the Azure portal.

At this point I dont believe that any one of them is any better or reliable than the others.

> There are currently no active events. Use Azure Service Health to view other issues that may be impacting your services.

Links to a page on Azure Portal which is down...

"We are investigating an issue with the Azure Portal where customers may be experiencing issues accessing the portal. More information will be provided shortly."

> Big Tech lobbying is riding the EU’s deregulation wave by spending more, hiring more, and pushing more, according to a new report by NGO’s Corporate Europe Observatory and LobbyControl on Wednesday (29 October).

> Based on data from the EU’s transparency register, the NGOs found that tech companies spend the most on lobbying of any sector, spending €151m a year on lobbying — a 33 percent increase from €113m in 2023.

Gee whizz, I really do wonder how they end up having all the power!

[0] https://news.ycombinator.com/item?id=45744973

Decentralisation is winning it seems.

I think the response lies in the surrounding ecosystem.

If you have a company it's easier to scale your team if you use AWS (or any other established ecosystem). It's way easier to hire 10 engineers that are competent with AWS tools than it is to hire 10 engineers that are competent with the IBM tools.

And from the individuals perspective it also make sense to bet on larger platforms. If you want to increase your odds of getting a new job, learning the AWS tools gives you a better ROI than learning the IBM tools.

Pick your point on the scale

https://en.wikipedia.org/wiki/Natural_monopoly

In our highly interconnected world, decentralization paradoxically requires a central authority to enforce decentralization by restricting M&A, cartels, etc.

Stonks

And more importantly nobody lose any reputation except AWS/Azure/Google.

The real reason is that outages are not your fault. Its the new version of "nobody ever got fired for buying IBM" - later it became MS, and now its any big cloud provider.

On the merits though, I agree, haven’t had any serious issues with Hetzner.

It's only after the fact they are transparent about the impact

Can't help but smirk as my country is ramming through "Digital ID" right now

Unsubstantiated idea: So the support contract likely says there is a window between each reporting step and the status page is the last one and the one in the legal documents giving them several more hours before the clauses trigger.

Much of Xbox is behind that too.

This message was last updated at 16:35 UTC on 29 October 2025”

That said, I don't hear about GCP outages all that often. I do think AWS might be leading in outages, but that's a gut feeling, I didn't look up numbers.

It's not easy though.

Unless that's a euphemism for "vibe coding", no.

> We have confirmed that an inadvertent configuration change as the trigger event for this issue.

Save the speculation for Reddit. HN is better than that.

FD and CDN are global resources and are experiencing issues. Probably some other global resources as well.

Hate to say it, but DNS is looking like it's still the undisputed champ.

Edit: nope looks like there's actually a spike on GCP as well

But what if I don't want AI brought to me?

    > “Microsoft is being recognized and rewarded at levels never seen before,” Nadella wrote. “And yet, at the same time, we’ve undergone layoffs. This is the enigma of success in an industry that has no franchise value.”
     
    > Nadella explained the disconnect between thriving financials and layoffs by stating that “progress isn’t linear” and that it is “sometimes dissonant, and always demanding.”

    > These decisions are among the most difficult we have to make. They affect people we’ve worked alongside, learned from, and shared countless moments with—our colleagues, teammates, and friends.