Error on lookup for scoped packages (Invalid status code 503)

jspm / npm

NPM Location Service

19 stars 34 forks source link

Error on lookup for scoped packages (Invalid status code 503) #117

Closed teohhanhui closed 8 years ago

teohhanhui commented 8 years ago

with jspm 0.16.19

warn Error on lookup for npm:@cycle/fetch
     Invalid status code 503

err  Error looking up npm:@cycle/fetch.

It was working before... And just stopped working with no changes on my end.

teohhanhui commented 8 years ago

It seems to work sometimes... Is this an npm registry issue? But would be strange if it only happens to scoped packages...

guybedford commented 8 years ago

Yes this would be due to instability in the npm registry (500 error and all).

teohhanhui commented 8 years ago

For those who were wondering:

Jan 27, 2016

Intermittent scoped module installation failures from US East

The registry was returning elevated rates of 503s from a specific origin host that US East users were likely to be routed to. This was due to a misconfiguration that caused requests to an internal service to be rejected. This configuration has been corrected. 503 rates are back down to normal. Jan 27, 17:31 UTC

http://status.npmjs.org/