raphaelyancey commented 4 years ago

What / Why

I'm getting E429 error

When

Everytime I run npm ci (since today at least)

Where

npm public registry

Current Behavior

The npm ci command returns E429 error (Too Many Requests) and doesn't complete packages installation

Steps to Reproduce

npm ci

Expected Behavior

It should install packages

anton-bot commented 4 years ago

NPM: Not Performing on Mondays

roppazvan commented 4 years ago

NPM: No Problem Monday

kiknaio commented 4 years ago

Same issue within Gitlab runners

nandueverurs commented 4 years ago

Same issue when tried a build in heroku . CF-error-code 1015.

The owner of this website (registry.npmjs.org) has banned you temporarily from accessing this website

slashd0t commented 4 years ago

I also got this error when I execute the npm install command: "Access denied | registry.npmjs.org used Cloudflare to restrict access. You are being rate limited. The owner of this website (registry.npmjs.org) has banned you temporarily from accessing this website.". I'm from Cebu Philippines. Is this CloudFlare issue or the NPM ?

jimhooker2002 commented 4 years ago

download

mkarkash commented 4 years ago

The owner of this website (registry.npmjs.org) has banned you temporarily from accessing this website.

SargoDarya commented 4 years ago

Hey folks, as much fun as this might be please let us restrict this to actually useful stuff so people can start working again.

gmemstr commented 4 years ago

It looks like this issue is pretty widespread, rather than everyone posting "this is happening to me on X" how about we hang tight until we hear something from NPM? Or we can +1 a comment if affected.

anton-bot commented 4 years ago

NPM: Not a Package Manager

stephnr commented 4 years ago

We are getting outtages here in Sweden too 👌 🙆‍♂

dorsharon commented 4 years ago

It looks like this issue is pretty widespread, rather than everyone posting "this is happening to me on X" how about we hang tight until we hear something from NPM? Or we can +1 a comment if affected.

Nah, memes and useless comments for the win

anaelsh commented 4 years ago

Having the same issue on AWS build

jacob-j commented 4 years ago

Does this mean we can leave for second lunch?

rmothilal commented 4 years ago

Having the same issue on CircleCi Builds

kapik commented 4 years ago

Having the same issue on Github Actions !

break-pointer commented 4 years ago

Time to install https://github.com/verdaccio/verdaccio/

ksemtinimahmoud commented 4 years ago

anant-k-singh commented 4 years ago

Wow, Memes in comments XD

phaberest commented 4 years ago

Guys it's awesome to be all on the same boat and share some love while we stress out, but...could we stop telling each other "me too"?

Memes are always welcomed, btw!

quite commented 4 years ago

This is the consequence of over-reliance on somebody else's computer. @phaberest you're senseless and I am too :-}

aleczratiu commented 4 years ago

giphy

JavierPons commented 4 years ago

same!

jimmycasey commented 4 years ago

NPM just told me we can take the rest of the day off, thanks folks.

prasadkadiyala commented 4 years ago

Same issue here

DennisSkoko commented 4 years ago

3pg17i

AkuSilvenius commented 4 years ago

Does this still apply?

segl84 commented 4 years ago

Same

roppazvan commented 4 years ago

Npm headquarters right now:

I assume the npmjs office right now #npm pic.twitter.com/wZy0Bo3PM8
— Nick Hammond (@thehappypenguin) February 17, 2020

nikiamnik commented 4 years ago

Issue is now fixed

https://status.npmjs.org/ is till green 💃

tim-dewit commented 4 years ago

NPM: NPM

anton-bot commented 4 years ago

Rumours say NPM packages have been infected with a coronavirus

ovr commented 4 years ago

I think it's a good example why it's highly recommended installing own npm registry/proxy to protect similar issues when you will not able to deploy your app due NPM registry outage