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 8 hours ago [-]
It's not DNS
There's no way it's DNS
It was DNS
- SSBroski
corvad 9 hours ago [-]
Just wait and it will be something like "Github's internal DNS was down and caused widespread service communication issues."
xaxfixho 8 hours ago [-]
it might just be *AZURE*
Imustaskforhelp 9 hours ago [-]
I am waiting for jeff geerling's "its always dns" t-shirt reference/video about it if that's the case.
Scipio_Afri 9 hours ago [-]
Easy there buddy, not everything needs to be a polymarket bet :-)
lots of amazon pages & search seem to be degraded as well
cozzyd 9 hours ago [-]
That's one way to fix supply chain vulnerabilities.
tantalor 9 hours ago [-]
Can't have any vulnerabilities if you don't have a supply chain
nine_k 8 hours ago [-]
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 8 hours ago [-]
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 5 hours ago [-]
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 6 hours ago [-]
> 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 8 hours ago [-]
Only if we had a turn key distributed cache, like IPFS
ibejoeb 8 hours ago [-]
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.
zadikian 6 hours ago [-]
Presumably, how ever you mark a version as latest would also be how you mark one as compromised. IPFS files are immutable and keyed by hash. But this seems like overengineering.
cluckindan 8 hours ago [-]
Waiting for the BitTorrent package manager
XorNot 8 hours ago [-]
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 7 hours ago [-]
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 8 hours ago [-]
Hold the jokes until we're sure this isn't an `.unwrap()`
normie3000 9 hours ago [-]
Well it is owned by github.
cute_boi 9 hours ago [-]
which is owned by microslop
rvz 9 hours ago [-]
...and proudly maintained by Microsoft's AI agents: Tay.ai, Zo, and Copilot.
They seem to be doing a pretty good job at wrecking both GitHub and npm at the same time.
I mean more like a full git competitor. Gitlab exists but more competition is generally better for the consumer and it looks like Github's lead is starting to falter with all these incidents.
sofixa 8 hours ago [-]
GitLab is right there. And overall provides a better product than GitHub, if nothing else on these two points:
* You can actually have an organisational structure (folders/namespaces), and projects can be moved around with automatic redirects. Also, inheritance of access controls, variables between the namespaces
* GitLabCI is organised in a way that makes supply chain attacks less of a risk. GitHub Actions takes the NPM/JS approach, where every step is an action, one you usually need to get off someone, with shoddy versioning, tons of transient dependencies, etc. In GitLabCI you can have templates, but you don't have to use an external template for every bit. It's shell scripting on top of containers, so you can have custom container images with your stuff, or custom scripts, or templates that bundle it all.
justinclift 8 hours ago [-]
GitLab also limits the size of PRs/MRs, which makes it Unfit for Purpose. :( :( :(
Its a problem they know about, but have no plan to fix before 2027.
irishcoffee 8 hours ago [-]
I mean, the PR limit is like a million characters. I would also reject a PR of a million characters. That’s bananas.
justinclift 7 hours ago [-]
Not sure about that "million characters", but we've been bitten by it in our production systems. :(
Thus, we're moving off GitLab.
skullone 5 hours ago [-]
What use case does a million character PR have?
irishcoffee 7 hours ago [-]
I'm sure, I looked it up.
8 hours ago [-]
fontain 8 hours ago [-]
All of those features are supported by GitHub in some form, e.g: Organizations can now belong to Enterprises.
sofixa 29 minutes ago [-]
It's not the same, at all.
SSO, access tokens, secrets are all bound to the Organization level - if you work on multiple Organizations you have to log in separately... You also cannot have nested Organizations.
dijksterhuis 7 hours ago [-]
tree based directory structure stuff is available on gitlab’s free tier — so are all the permissions inheritance for groups etc.
so, while you’re technically right, these features are apparently paywalled heavily on github.
ime you get more features on gitlab for the same price (or less). i switched fully two years ago and im not going back.
dmitrygr 7 hours ago [-]
libc is still working just fine, as is the linux kernel. Mayhaps having 2000 dependencies on 3000 packages from 4000 unvetted sources was a mistake afterall?
TesterVetter 9 hours ago [-]
[dead]
cute_boi 9 hours ago [-]
microslop slops are down.
12345hn6789 9 hours ago [-]
Azure is completely dead across multiple resources. Confirming....
[0] https://arstechnica.com/information-technology/2026/01/odd-a...
Ironically, both Nandu and Verdaccio are implemented in Tyepscript and install via npm.
(Same logic obviously applies to Python packages, Docker images, etc.)
I took that for granted back then and just assumed it was standard enterprise policy
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.
Both yarn and pnpm support http/2 which speeds up the bazillion requests quite a bit.
They seem to be doing a pretty good job at wrecking both GitHub and npm at the same time.
Keep up the good work Microsoft.
Let's shoot for 100% downtime though. Thanks.
https://developers.cloudflare.com/artifacts/
* You can actually have an organisational structure (folders/namespaces), and projects can be moved around with automatic redirects. Also, inheritance of access controls, variables between the namespaces
* GitLabCI is organised in a way that makes supply chain attacks less of a risk. GitHub Actions takes the NPM/JS approach, where every step is an action, one you usually need to get off someone, with shoddy versioning, tons of transient dependencies, etc. In GitLabCI you can have templates, but you don't have to use an external template for every bit. It's shell scripting on top of containers, so you can have custom container images with your stuff, or custom scripts, or templates that bundle it all.
Its a problem they know about, but have no plan to fix before 2027.
Thus, we're moving off GitLab.
SSO, access tokens, secrets are all bound to the Organization level - if you work on multiple Organizations you have to log in separately... You also cannot have nested Organizations.
so, while you’re technically right, these features are apparently paywalled heavily on github.
ime you get more features on gitlab for the same price (or less). i switched fully two years ago and im not going back.
:)