We added a preflight curl against registry.npmjs.org before the install step in CI. Not surprising they went down together.

I bet 10 dollars it's DNS.

Nah, can't be, Azure DNS has a 100% SLA after all: https://learn.microsoft.com/en-us/azure/dns/dns-faq#what-is-...

"Always" up, but maybe not going where you expect. [0]

[0] https://arstechnica.com/information-technology/2026/01/odd-a...

To be fair, it feels like the DNS service has been the most reliable part of our Azure infra. Never really had issues with it, whether with traffic or API calls.

  It's not DNS
  There's no way it's DNS
  It was DNS

- SSBroski

It's DNS

If it's not DNS it's MTU if you're a person and BGP if you're a company.

Just wait and it will be something like "Github's internal DNS was down and caused widespread service communication issues."

I am waiting for jeff geerling's "its always dns" t-shirt reference/video about it if that's the case.

Easy there buddy, not everything needs to be a polymarket bet :-)

it might just be *AZURE*

It's likely someone just ran npm ls -all