At this stage, we anticipate full mitigation within the next four hours as we continue to recover nodes. This means we expect recovery to happen by 23:20 UTC on 29 October 2025. We will provide another update on our progress within two hours, or sooner if warranted.

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

CSAM apparently also means Customer Success Account Manager for those who might have gotten startled by this message like me.

Some really unfortunate acronyms flying around the Microsoft ecosystem . . .

Back when we used Azure the only outcome was them trying to upsell us on Premium Support

in many cases: no service health alerts, no status page updates and no confirmations from the support team in tickets. still we can confirm these issues from different customers accross europe. Mostly the issues are regional dependent.

> CSAM

Child Sex-Abuse Material?!? Well, a nice case of acronym collision.

Where do these alerts supposedly come from? I started having issues around 4PM (GMT), couldn't access portal, and couldn't make AKV requests from the CLI, and initially asked our Ops guys but with no info and a vague "There may be issues with Portal" on their status page, that was me done for the day.

I got a service health alert an hour after it started, saying the portal was having issues. Pretty useless and misleading.

so true. instead of getting a fast feedback we are wasting time searching for our own issues first.

That RCA was fun. A distributed system with members that don't know about each other, don't bother with leader elections, and basically all stomp all over each other updating the records. It "worked fine" until one of the members had slightly increased latency and everything cascade-failed down from there. I'm sure there was missing (internal) context but it did not sound like a well-architected system at all.

https://isitdns.com/

It's always DNS

That's three of the hardest problems in CS ))

Didn't the underlying vendor they used for Azure Front Door go bankrupt? It's probably on life support.

They re-added it once the site was accessible.

It's a Sev 0 actually (as one would expect - this isn't a big secret). I was on the engineering bridge call earlier for a bit. The Azure service I work on was minimally impacted (our customer facing dashboard could not load, but APIs and data layer were not impacted) but we found a workaround.

It was here https://news.ycombinator.com/item?id=45749054 but that comment has been deleted.

From what I can tell, Downdetector just tracks traffic to their pages without actually checking if the site is down.

The other day during the AWS outage they "reported" OVH down too.

yea I saw that, but im not sure on how accurate that is. a few large apps/companies I know to be 100% on AWS in us-east-1 are cranking along just fine.

Not sure if this is true. I just login to the console with no glitch.

AWS was performance issues and I believe is resolved.

Unless you pay for CloudFlare’s Enterpise plan, you’re required to have them host your DNS zone, you can use a different registrar as long as you just point your NS records to Cloudflare.

Be aware that if you’re using Azure as your registrar, it’s (probably still) impossible to change your NS records to point to CloudFlare’s DNS server, at least it was for me about 6 months ago.

This also makes it impossible to transfer your domain to them either, as CloudFlare’s domain transfer flow requires you set your NS records to point to them before their interface shows a transfer option.

In our case we had to transfer to a different registrar, we used Namecheap.

However, transferring a domain from Azure was also a nightmare. Their UI doesn’t have any kind of transfer option, I eventually found an obscure document (not on their Learn website) which had an az command which would let you get a transfer code which I could give to Namecheap.

Then I had to wait over a week for the transfer timeout to occur because there is no way on Azure side that I could find to accept the transfer immediately.

I found CloudFlare’s way of building rules quite easy to use, different from Front Door but I’m not doing anything more complex than some redirects and reverse proxying.

I will say that Cloudflare’s UI is super fast, with Front Door I always found it painfully slow when trying to do any kind of configuration.

Cloudflare also doesn’t have the problem that Front Door has where it requires a manual process every 6 months or so to renew the APEX certificate.