NPM: Issues with package install, package publish, and login
status.npmjs.org
NPM: Issues with package install, package publish, and login
1–10 of 10 posts
Re: NPM: Issues with package install, package publish, and login
#2Wonder if this is at all related to the GCP outage
Re: NPM: Issues with package install, package publish, and login
#3Wonder if this is at all related to the GCP outage
there is also some kind of cloudflare outage: https://www.cloudflarestatus.com/
Re: NPM: Issues with package install, package publish, and login
#4Wonder if this is at all related to the GCP outage
there is also some kind of cloudflare outage: https://www.cloudflarestatus.com/
And Copilot model hosting outage and even AWS outage https://www.githubstatus.com/
https://downdetector.com/status/aws-amazon-web-services/
Re: NPM: Issues with package install, package publish, and login
#5Earlier quoted context omitted.
there is also some kind of cloudflare outage: https://www.cloudflarestatus.com/
And Copilot model hosting outage and even AWS outage https://www.githubstatus.com/ https://downdetector.com/status/aws-amazon-web-services/
And as a general timeline (IF status times are accurate. I trust the AWS the most due to the down detector stuff, which means it really could be all at the same time anyway due to lag in self-reporting incidents)
~1:00 CT: AWS outage start, GCP outage start
~1:15 CT: NPM registry
~1:19 CT: Github & Cloudflar
Re: NPM: Issues with package install, package publish, and login
#6Re: NPM: Issues with package install, package publish, and login
#7Earlier quoted context omitted.
there is also some kind of cloudflare outage: https://www.cloudflarestatus.com/
registry.npmjs.org is cloudflare, so that's probably it although I wonder why multiple independent platforms are affected all at once?
> registry.npmjs.org is cloudflare...
source? looked briefly for info on this but came up with nothing
Re: NPM: Issues with package install, package publish, and login
#8Earlier quoted context omitted.
registry.npmjs.org is cloudflare, so that's probably it although I wonder why multiple independent platforms are affected all at once?
> registry.npmjs.org is cloudflare... source? looked briefly for info on this but came up with nothing
whois the IP it resolves to
whois $(dig registry.npmjs.org +short | head -n1)Re: NPM: Issues with package install, package publish, and login
#9Right on the day that I cancelled all meetings to have a productive coding day!
Re: NPM: Issues with package install, package publish, and login
#10[deleted]