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
www ? Operational
replicate.npmjs.com ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
Registry Uptime
Fetching
Registry Response Time
Fetching
Website Uptime
Fetching
Website Response Time
Fetching
Past Incidents
Jan 17, 2017

No incidents reported today.

Jan 16, 2017

No incidents reported.

Jan 15, 2017

No incidents reported.

Jan 14, 2017

No incidents reported.

Jan 13, 2017
briefly, between (2:54 - 2:58PM PDT) we saw a increase in origin latency, resulting in increased 503s from the registry; the problem has been resolved and we are investigating the underlying cause.
Jan 13, 23:03 UTC
Jan 12, 2017

No incidents reported.

Jan 11, 2017

No incidents reported.

Jan 10, 2017

No incidents reported.

Jan 9, 2017

No incidents reported.

Jan 8, 2017

No incidents reported.

Jan 7, 2017

No incidents reported.

Jan 6, 2017

No incidents reported.

Jan 5, 2017
Resolved - All services back to normal.
Jan 5, 05:23 UTC
Monitoring - We have successfully failed over to our secondary & removed the temporary workaround.
Jan 5, 04:51 UTC
Identified - We indeed lost a database primary host. We are failing over to the secondary now. In the meantime, we've deployed a workaround that restores website functionality, albeit with no billing data. The website will temporarily report placeholder billing data; this workaround will be backed out shortly.
Jan 5, 04:32 UTC
Investigating - Our website is not responding to requests right now. An instance providing a backing service has gone down. We are in the process of restarting and/or replacing the downed host.
Jan 5, 04:24 UTC
Jan 4, 2017

No incidents reported.

Jan 3, 2017

No incidents reported.