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
Sep 1, 2014

No incidents reported today.

Aug 31, 2014

No incidents reported.

Aug 30, 2014

No incidents reported.

Aug 29, 2014
Resolved - This incident has been resolved.
Aug 29, 05:05 UTC
Identified - We pushed an update to the registry couchapp that triggered a view-generation cycle in our downstream CouchDB instances, unfortunately not realizing that the website was accessing the read-only replicas for this data rather than accessing the root database directly. That is, while we did wait for view generation to complete before copying the data to the production design doc, but did not wait for view generation to complete on *all* of the downstream couches.

As a result, the "Browse" pages and homepage are showing outdated and incorrect data. This problem will correct itself as the view generation completes in the read-only replicas, and the website will show accurate data shortly.

Our internal process is being updated to prevent this from happening again in the future.
Aug 28, 23:44 UTC
Aug 27, 2014
The API at api.npmjs.org/downloads/ was unavailable for 1 hour. There was no associated website downtime.
Aug 27, 20:23 UTC
Aug 26, 2014

No incidents reported.

Aug 25, 2014

No incidents reported.

Aug 24, 2014

No incidents reported.

Aug 23, 2014
From 1330 to 1501 UTC today, customers served by our Australian CDN point of presence (users in Australia and nearby parts of southeast Asia and the Pacific) were receiving 503s as a result of an issue with that PoP. At peak, this affected 5% of active users. It was resolved by our CDN provider.
Aug 23, 15:56 UTC
Aug 22, 2014
From 4-5pm Pacific Time, the website was sending 503s to at most 3% of users. This was due to network problems on one of the www servers. That server was removed from rotation and full service was restored.
Aug 22, 00:35 UTC
Aug 21, 2014

No incidents reported.

Aug 20, 2014

No incidents reported.

Aug 19, 2014

No incidents reported.

Aug 18, 2014

No incidents reported.