All Systems Operational

About This Site

npm loves you. Here is some info about how well it's doing.

Registry Reads?
Website Reads?
US East (NYC)
US East (ASH)
US East (IAD)
US East (ATL)
US Central (DAL)
US Central (CHI)
US West (LAX)
US West (SJC)
Europe (FRA)
Europe (AMS)
Europe (LON)
Asia/Pacific (AU)
Asia/Pacific (TYO)
Asia/Pacific (NZ)
Asia/Pacific (SIN)
ec2-us-east-1
ec2-us-west-2
Operational
Degraded Performance
Partial Outage
Major Outage
System Metrics Month Week Day
Registry Uptime
fetching...
Registry Response Time
fetching...
Website Uptime
fetching...
Website Response Time
fetching...
Past Incidents
Oct 2, 2014

No incidents reported today.

Oct 1, 2014

No incidents reported.

Sep 30, 2014

No incidents reported.

Sep 29, 2014

No incidents reported.

Sep 28, 2014

No incidents reported.

Sep 27, 2014

No incidents reported.

Sep 26, 2014

No incidents reported.

Sep 25, 2014
Postmortem - Read details
Sep 25, 20:10 UTC
Resolved - All replicas are now back up to date.
Sep 25, 20:02 UTC
Update - The configuration error responsible has been identified and is being fixed.
Sep 25, 20:00 UTC
Identified - The primary npm, Inc. registry is having issues replicating newly-published packages between its write master CouchDB and its read replicas. Packages publish successfully, but are not installable via the npm client because they have not yet been published out to the replicas. We are investigating the situation and hope to have it resolved shortly.
Sep 25, 19:44 UTC
Sep 24, 2014
Although the npm client supports scoped packages, the public npm registry does not yet fully support them. We put code in place to prevent packages with scopes being accidentally pushed to the registry before we had completed the necessary work, but a bug in that code allowed 2 scoped packages to be published.

This broke some down-stream follower applications -- we expected that would happen, which is why we hadn't intended to allow scoped packages to publish yet. The bug that allowed the 2 packages in has been fixed, and those 2 packages deleted. If you run a follower, you should confirm that you are up to date and skip both the revs including the scoped packages and if necessary also the revs deleting them.

Our apologies for this incident. Scoped packages are coming to the public registry later this year, but will require explicitly switching to a new upstream host to avoid this kind of incompatibility.
Sep 24, 18:53 UTC
Sep 23, 2014

No incidents reported.

Sep 22, 2014

No incidents reported.

Sep 21, 2014

No incidents reported.

Sep 20, 2014

No incidents reported.

Sep 19, 2014

No incidents reported.

Sep 18, 2014

No incidents reported.