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.55 % uptime
Today
npm package search ? Operational
90 days ago
100.0 % uptime
Today
npm Enterprise Operational
90 days ago
100.0 % uptime
Today
npm Security Audit Operational
90 days ago
100.0 % 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
Past Incidents
Feb 18, 2020

No incidents reported today.

Feb 17, 2020
Resolved - Thank you to our users for their reports of success, and patience while engineers from npm and our partners worked together to isolate the cause of this incident. Our content delivery partner investigated as soon as we contacted them and started immediately to deploy a fix, which worked right away.

Just now, we took some time to catch up with a handful of users who were experiencing what are now known to be unrelated issues.
So, presently we can confirm that the registry is fully functional.

We’d like to thank our support and technical staff for their unreserved help on a holiday, and again thank the community for understanding.
Feb 17, 17:59 UTC
Monitoring - Our content delivery partner has informed us they've implemented a fix. We are monitoring.
Feb 17, 13:07 UTC
Investigating - We are currently investigating 403 / 429 errors received by some users.
Feb 17, 12:51 UTC
Feb 16, 2020

No incidents reported.

Feb 15, 2020

No incidents reported.

Feb 14, 2020

No incidents reported.

Feb 13, 2020
Postmortem - Read details
Feb 13, 16:16 UTC
Resolved - Thanks for your patience. The issues we identified today have been resolved.
Feb 13, 03:38 UTC
Update - We are continuing to investigate this issue.
Feb 13, 00:10 UTC
Update - We're continuing to look into this issue. For most users, we're at 100% functionality. Some, unfortunately, will see 404s.
We are seeing a pattern with packages that have the word "error" in their name.
Just a reminder that we recommend using `npm ci` and not `npm i` in your automated CI/CD pipelines.
And, please, help me in thanking our engineering staff. They have delivered fast teamwork from around the world in response to your reports. We really appreciate the community feedback.
Feb 13, 00:09 UTC
Investigating - We are investigating a separate issue where some users are noticing 404's, and we're noticing different results depending on location.

It seems like this occurs on packages with `error` in their name, and varies by location.

Thank you for your patience while we investigate further.
Feb 12, 20:36 UTC
Feb 12, 2020
Resolved - Our team has finished fixing the metadata permissions issue on the remaining packages. We're seeing that has resolved the issue. Thanks for your patience.
Feb 12, 19:25 UTC
Update - Some package metadata for a select few public packages was stored with incorrect permissions (too restrictive.)
We're fixing them, purging the incorrect 404's from the cache, and you should see positive results very soon.

A bit of detail: We've found this problem is only occurring with minified package metadata. The npm client automatically falls back to fetching the full package metadata when that's not available.

For other use cases: our developers are working to restore full functionality at this time. Thanks for your patience.
Feb 12, 17:54 UTC
Identified - We've found some further issues that are causing disruption of service to select geographic regions, for some select packages. We are currently implementing more fixes to restore 100% functionality to all regions.
Feb 12, 17:19 UTC
Update - We are continuing to monitor for any further issues.
Feb 12, 13:37 UTC
Update - We are continuing to monitor for any further issues.
Feb 12, 13:17 UTC
Monitoring - We believe we have identified the current issue with 404 errors on specific packages in specific world regions, and a fix has been applied.

It will take some time to propagate across all our nodes and CDN layer.
We will keep this incident open until the issue has fully propagated.
Feb 12, 13:10 UTC
Investigating - We are currently investigating issues with installing certain packages.

Some of the packages known to be affected are: 3d-view, error-ex ,42-cent-base, 8base-cli.
Feb 12, 13:04 UTC
Feb 11, 2020
Resolved - This incident has been resolved.
Feb 11, 16:21 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 10, 20:47 UTC
Update - We have identified the configuration issue that was causing problems for some package publish operations, and we've fixed it.

If you had issues publishing packages within the last three hours, please retry now.
Feb 10, 20:46 UTC
Identified - We've identified an issue which has caused newly published packages to be invisible.

We've figured out why and we're working on a resolution.
Feb 10, 20:14 UTC
Feb 9, 2020

No incidents reported.

Feb 8, 2020

No incidents reported.

Feb 7, 2020

No incidents reported.

Feb 6, 2020

No incidents reported.

Feb 5, 2020

No incidents reported.

Feb 4, 2020

No incidents reported.