Get the top HN stories in your inbox every day.
corvad
I wonder if this is an underlying infra issue with Azure being that Github was also having issues.
nulltrace
We added a preflight curl against registry.npmjs.org before the install step in CI. Not surprising they went down together.
2ndorderthought
I bet 10 dollars it's DNS.
thanatos_dem
Nah, can't be, Azure DNS has a 100% SLA after all: https://learn.microsoft.com/en-us/azure/dns/dns-faq#what-is-...
shakna
"Always" up, but maybe not going where you expect. [0]
[0] https://arstechnica.com/information-technology/2026/01/odd-a...
parliament32
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
It's not DNS
There's no way it's DNS
It was DNS
- SSBroskicorvad
Just wait and it will be something like "Github's internal DNS was down and caused widespread service communication issues."
xaxfixho
it might just be *AZURE*
Imustaskforhelp
I am waiting for jeff geerling's "its always dns" t-shirt reference/video about it if that's the case.
Scipio_Afri
Easy there buddy, not everything needs to be a polymarket bet :-)
munk-a
It's likely someone just ran npm ls -all
airstrike
https://www.ebay.com/ is also down
Raed667
lots of amazon pages & search seem to be degraded as well
cozzyd
That's one way to fix supply chain vulnerabilities.
tantalor
Can't have any vulnerabilities if you don't have a supply chain
nine_k
More seriously, keeping a local cache of external npm packages, and a local artifact storage for internal npm packages looks like a wise thing to have done long ago. Might be cheaper in the long run.
Ironically, both Nandu and Verdaccio are implemented in Tyepscript and install via npm.
(Same logic obviously applies to Python packages, Docker images, etc.)
hmokiguess
At my former job we had a private registry that was a mirror of npm’s with an approval gate for packages devs would request and it would always pin versions
I took that for granted back then and just assumed it was standard enterprise policy
jamesfinlayson
Multiple previous jobs had this too (local Packagist is thing, Artifactory is another) but my current job got rid of theirs. Seemed a little short-sighted given the risks but I don't make the decisions.
spartanatreyu
> a local artifact storage for internal npm packages looks like a wise thing to have done long ago
Deno already does this invisibly by default.
All packages are stored in the global cache.
No need to store multiple versions of the same dependencies across projects.
To the code in your projects: there is no such thing as a global cache. Just import your dependencies like normal and deno maps them to the global cache.
miohtama
Only if we had a turn key distributed cache, like IPFS
ibejoeb
Does IPFS support content eviction now? If not, that could go wrong really fast. You get a compromised package out there and then, I think, literally every node needs to unpin it or it remains.
cluckindan
Waiting for the BitTorrent package manager
XorNot
Caching NPM was easier when you could pull the Couchbase replicate API. Afaik that's gone and now you just have to send a bazillion http requests instead.
nine_k
Sending a bazillion http requests within your LAN, or at least your VPC, is much easier, faster, and cheaper.
Both yarn and pnpm support http/2 which speeds up the bazillion requests quite a bit.
hexasquid
Hold the jokes until we're sure this isn't an `.unwrap()`
lrvick
Whenever NPM is offline, the internet is a little safer.
Keep up the good work Microsoft.
Let's shoot for 100% downtime though. Thanks.
normie3000
Well it is owned by github.
squarefoot
Ebay is also down. https://www.isitdownrightnow.com/ebay.com.html
corvad
Fixed as of 22:30 UTC. Hope there's a postmortem.
saadn92
ha, github is down too
simjnd
https://npmx.dev is not
dabinat
Tailscale too: https://status.tailscale.com/
Get the top HN stories in your inbox every day.
First GitHub, now NPM? Oh no... That is happening, guys. Rise of the machines. I hope Jira is next and Slack follows.