All Systems Operational

About This Site

npm loves you. Here is some info about how well it's doing. (You can also follow these updates at @npmstatus on Twitter!)

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
Package publishing Operational
90 days ago
99.99 % uptime
Today
npm package search ? Operational
90 days ago
100.0 % uptime
Today
npm Enterprise Operational
90 days ago
99.94 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
had a major outage
had a partial outage
Registry Uptime
Fetching
Registry Response Time
Fetching
Website Uptime
Fetching
Website Response Time
Fetching
Past Incidents
Jun 18, 2019

No incidents reported today.

Jun 17, 2019

No incidents reported.

Jun 16, 2019

No incidents reported.

Jun 15, 2019

No incidents reported.

Jun 14, 2019

No incidents reported.

Jun 13, 2019

No incidents reported.

Jun 12, 2019
Resolved - The ranking process in the search indexing of packages will exclude some low-quality packages from the search index. It is expected that not all packages for a specific author will be indexed in the search process and package counts can differ from the npm registry and the search results.
Jun 12, 14:04 UTC
Investigating - We are currently investigating this issue.
Jun 11, 15:15 UTC
Jun 10, 2019

No incidents reported.

Jun 9, 2019

No incidents reported.

Jun 8, 2019

No incidents reported.

Jun 7, 2019

No incidents reported.

Jun 6, 2019

No incidents reported.

Jun 5, 2019
Resolved - This incident has been resolved.
Jun 5, 01:42 UTC
Identified - The issue has been identified and a fix is being implemented.
May 31, 15:04 UTC
Update - We are continuing to investigate this issue.
May 31, 12:24 UTC
Investigating - We are currently investigating this issue.
May 31, 12:22 UTC
Jun 4, 2019

No incidents reported.