All Systems Operational

About This Site

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

Registry Reads ? Operational
Website Reads ? Operational
US East (NYC) Operational
US East (ASH) Operational
US East (IAD) Operational
US East (ATL) Operational
US Central (DAL) Operational
US Central (CHI) Operational
US West (LAX) Operational
US West (SJC) Operational
Europe (FRA) Operational
Europe (AMS) Operational
Europe (LON) Operational
Asia/Pacific (AU) Operational
Asia/Pacific (TYO) Operational
Asia/Pacific (NZ) Operational
Asia/Pacific (SIN) Operational
ec2-us-east-1 Operational
ec2-us-west-2 Operational
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
Feb 7, 2016

No incidents reported today.

Feb 6, 2016

No incidents reported.

Feb 5, 2016
Resolved - Publications are back to normal.
Feb 5, 00:33 UTC
Monitoring - Replication has been repaired and all endpoints are now up to date with reality.
Feb 5, 00:25 UTC
Identified - There is an ongoing delay with replication of new package publishes. Publishes are successful but are not visible everywhere. Engineers are working on the issue and we will update shortly.
Feb 5, 00:15 UTC
Monitoring - Publications were failing because of a bug in our new publication flow that stacked up open connections to the registry write primary. We've rolled back to earlier code that is a little slower but doesn't leak connections while we debug the problem in our testing environment. Publications should now be succeeding.
Feb 4, 23:43 UTC
Investigating - We are investigating failing writes to the registry.
Feb 4, 23:09 UTC
Feb 3, 2016

No incidents reported.

Feb 2, 2016

No incidents reported.

Feb 1, 2016

No incidents reported.

Jan 31, 2016

No incidents reported.

Jan 30, 2016
Our authentication services were briefly overloaded by an external event, leading to auth failures on package pages and the command line. Monitoring detected the incident and it was resolved after approximately 30 minutes of instability.
Jan 30, 08:10 UTC
Jan 29, 2016

No incidents reported.

Jan 28, 2016
The registry was returning elevated 503 rates to our users in Europe from 7:00 UTC to 13:00 UTC due to a misconfiguration of one of the package servers. Our apologies!
Jan 28, 23:16 UTC
Jan 27, 2016
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
Jan 26, 2016

No incidents reported.

Jan 25, 2016

No incidents reported.

Jan 24, 2016

No incidents reported.