I wonder if this is an underlying infra issue with Azure being that Github was also having issues.

▲ nulltrace 4 hours ago | parent | next [-]

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

▲ 2ndorderthought 4 hours ago | parent | prev | next [-]

I bet 10 dollars it's DNS.

▲ thanatos_dem 4 hours ago | parent | next [-]

	▲	shakna 3 hours ago \| parent \| next [-]
		"Always" up, but maybe not going where you expect. [0] [0] https://arstechnica.com/information-technology/2026/01/odd-a...
	▲	parliament32 3 hours ago \| parent \| prev [-]
		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.

▲ yomismoaqui 4 hours ago | parent | prev | next [-]

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

- SSBroski

▲ corvad 4 hours ago | parent | prev | next [-]

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

▲ xaxfixho 4 hours ago | parent | prev | next [-]

it might just be *AZURE*

▲ Imustaskforhelp 4 hours ago | parent | prev | next [-]

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

▲ Scipio_Afri 4 hours ago | parent | prev [-]

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

▲ munk-a 4 hours ago | parent | prev [-]

It's likely someone just ran npm ls -all