npm

First posted only after it was over

0% 0 of the 50 incidents we have in full detailbetterworse

The first update already said resolved. Typical vendor: 6%.

npm: lower than most vendors.

Time to resolve

2 h 18 min median; 9 in 10 within 4 h 46 minbetterworse

From the vendor’s own start and resolve times, last 365 days. Typical vendor: 2 h.

npm: around the middle.

Major or critical incidents

0.3 a month 4 in the last 365 daysbetterworse

Impact as the vendor labels it. Typical vendor: 1.2 a month.

npm: lower than most vendors.

Rewrites caught

None so far

Counts, not a rate: 10-minute tracking began Oct 17, so there are too few events to compare yet.

npm depends on

Runs in (named in its incidents): AWS us-east-1 (1).

Outage events: AWS us-west-2, Sep 3 (timing), Microsoft Azure west us, Jul 23 (timing), Cloudflare, Dec 5, 2025 (timing), AWS us-east-1, Oct 20, 2025 (timing), Google Cloud, Jun 12, 2025 (timing), Cloudflare, Oct 30, 2023 (timing), Cloudflare, Jun 21, 2022 (timing), Cloudflare, Dec 16, 2021 (timing) and 3 more.

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.

Full npm change history

No pricing, trust or legal pages tracked for npm.

Each change links to its diff: the changed passages with a few words of context, never a full copy of the page.

npm incidents, last 90 daysJSONMarkdown