CloudStatus

Npmjs Status Updates

500s on private scoped packages.

Apr 26, 00:22 UTC Identified - We have identified a configuration problem in a deploy and engineers are correcting it.Apr 26, 00:12 UTC Investigating - We are investigating an elevated rate of 500 responses returned during private package installation.

About 636 days ago - Tue 26 Apr 2016 00:22 (GMT)

Source: Npmjs - npm

Npmjs History

500s on private scoped packages.

Apr 26, 00:12 UTC Investigating - We are investigating an elevated rate of 500 responses returned during private package installation.

About 636 days ago - Tue 26 Apr 2016 00:14 (GMT)

More info

package tarballs availability in us-west

Apr 16, 02:00 UTC Resolved - metadata has been cleaned and failed versions have been removed where possible.Apr 15, 22:01 UTC Update - From 13:49 to 13:55 Pacific Time, one of our package servers was in a "wedged" state. Publishes that relied on this host during that period (about half of all publishes) appeared to succeed but in fact failed. As a result, approximately 50 packages have recently published versions that are missing their corresponding tarball file. We are identifying the failed publishes and removing them, so the affected packages will return to their last good version. Once cleanup is complete we will update this incident. If your package was affected, simply increment your patch version and re-publish. This will work even before cleanup is complete. Our apologies for the disruption.Apr 15, 20:58 UTC Monitoring - All tarballs hosts are back online and functioning. We're continuing to monitor.Apr 15, 20:54 UTC Identified - One of our packages tarballs hosts is experiencing difficulties. We're failing over to a hot spare but some users in the western US might observe difficulties installing during the cutover.

About 646 days ago - Sat 16 Apr 2016 02:01 (GMT)

More info

package tarballs availability in us-west

Apr 15, 22:01 UTC Update - From 13:49 to 13:55 Pacific Time, one of our package servers was in a "wedged" state. Publishes that relied on this host during that period (about half of all publishes) appeared to succeed but in fact failed. As a result, approximately 50 packages have recently published versions that are missing their corresponding tarball file. We are identifying the failed publishes and removing them, so the affected packages will return to their last good version. Once cleanup is complete we will update this incident. If your package was affected, simply increment your patch version and re-publish. This will work even before cleanup is complete. Our apologies for the disruption.Apr 15, 20:58 UTC Monitoring - All tarballs hosts are back online and functioning. We're continuing to monitor.Apr 15, 20:54 UTC Identified - One of our packages tarballs hosts is experiencing difficulties. We're failing over to a hot spare but some users in the western US might observe difficulties installing during the cutover.

About 646 days ago - Fri 15 Apr 2016 22:02 (GMT)

More info

package tarballs availability in us-west

Apr 15, 20:58 UTC Monitoring - All tarballs hosts are back online and functioning. We're continuing to monitor.Apr 15, 20:54 UTC Identified - One of our packages tarballs hosts is experiencing difficulties. We're failing over to a hot spare but some users in the western US might observe difficulties installing during the cutover.

About 646 days ago - Fri 15 Apr 2016 21:00 (GMT)

More info

package tarballs availability in us-west

Apr 15, 20:54 UTC Identified - One of our packages tarballs hosts is experiencing difficulties. We're failing over to a hot spare but some users in the western US might observe difficulties installing during the cutover.

About 646 days ago - Fri 15 Apr 2016 20:55 (GMT)

More info

garbled package metadata delivered to old npm clients

Apr 7, 03:36 UTC Resolved - We believe all package data with incorrect caching headers has been replaced in cache.Apr 6, 20:15 UTC Monitoring - A change made to the npm registry on 2016-04-04 unexpectedly triggered build failures for some users of older versions of the npm CLI (including those packaged by LTS OS distributions). A fix that the npm operational team rolled out was incomplete, but has since been correctly deployed across our infrastructure. Please see https://github.com/npm/npm/issues/12196#issuecomment-206525005 for more details.

About 654 days ago - Thu 7 Apr 2016 03:36 (GMT)

More info

garbled package metadata delivered to old npm clients

Apr 6, 20:15 UTC Monitoring - A change made to the npm registry on 2016-04-04 unexpectedly triggered build failures for some users of older versions of the npm CLI (including those packaged by LTS OS distributions). A fix that the npm operational team rolled out was incomplete, but has since been correctly deployed across our infrastructure. Please see https://github.com/npm/npm/issues/12196#issuecomment-206525005 for more details.

About 655 days ago - Wed 6 Apr 2016 20:16 (GMT)

More info

Partially-failed publications earlier today

Mar 25, 22:57 UTC Resolved - Failed versions have been cleaned up from metadata for nearly all of the packages affected. We were unable to repair 23 newly-published packages and will be in contact with the publishers.Mar 25, 21:41 UTC Monitoring - We are currently in the process of removing failed versions from package metadata. Most authors have already published newer versions to negate the severity of the failed publications. We appreciate your understanding and patience in this matter.Mar 25, 19:43 UTC Identified - We have identified 74 packages (with 83 total publications) affected by the misconfiguration. We are diligently working to fix the metadata for the failed versions so that they can be republished by their authors.Mar 25, 18:39 UTC Investigating - A bad configuration released at 17:39 UTC today caused package publications to fail partially, leaving an uninstallable version recorded in the package metadata. The visible symptom is that the registry will report that the version exists, but respond with a 404 when the tarball is requested. As of 18:15 UTC , the misconfiguration has been fixed, but we are investigating now to identify the packages affected & clean up the metadata.

About 667 days ago - Fri 25 Mar 2016 22:58 (GMT)

More info

Partially-failed publications earlier today

Mar 25, 21:41 UTC Monitoring - We are currently in the process of removing failed versions from package metadata. Most authors have already published newer versions to negate the severity of the failed publications. We appreciate your understanding and patience in this matter.Mar 25, 19:43 UTC Identified - We have identified 74 packages (with 83 total publications) affected by the misconfiguration. We are diligently working to fix the metadata for the failed versions so that they can be republished by their authors.Mar 25, 18:39 UTC Investigating - A bad configuration released at 17:39 UTC today caused package publications to fail partially, leaving an uninstallable version recorded in the package metadata. The visible symptom is that the registry will report that the version exists, but respond with a 404 when the tarball is requested. As of 18:15 UTC , the misconfiguration has been fixed, but we are investigating now to identify the packages affected & clean up the metadata.

About 667 days ago - Fri 25 Mar 2016 21:42 (GMT)

More info

Partially-failed publications earlier today

Mar 25, 19:43 UTC Identified - We have identified 74 packages (with 83 total publications) affected by the misconfiguration. We are diligently working to fix the metadata for the failed versions so that they can be republished by their authors.Mar 25, 18:39 UTC Investigating - A bad configuration released at 17:39 UTC today caused package publications to fail partially, leaving an uninstallable version recorded in the package metadata. The visible symptom is that the registry will report that the version exists, but respond with a 404 when the tarball is requested. As of 18:15 UTC , the misconfiguration has been fixed, but we are investigating now to identify the packages affected & clean up the metadata.

About 667 days ago - Fri 25 Mar 2016 19:44 (GMT)

More info