PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if npm Registry is down?

PulseWatch evaluates user reports and replay-approved automated evidence for npm Registry. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported npm Registry issues today?

As of Sep 25, 2026 20:19 UTC, 0 users had reported issues with npm Registry in the previous 24 hours.

How can I report a npm Registry outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Other

Is npm Registry down right now?

UnknownOfficial status last polled Sep 25, 2026 20:15 UTCwww.npmjs.com Official status page

Are you on the npm Registry team and see something inaccurate? Report it to us. We respond within one business day.

Is npm Registry down right now?

Unknown. npm Registry does not have a conclusive current status. The vendor reports operational; no fresh independent reachability check confirms it.

Status as of Sep 25, 2026 20:19 UTC

Unknown

npm Registry: status unknown

As of Sep 25, 2026 20:19 UTC

No product check is currently qualified to corroborate an incident for this service. Overall service status has not been established.

Reports 24h

Last incident

Sep 15, 2026 19:26 UTC

Trend

0/15m

Monitoring

Coverage gap

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for npm Registry.

Incident days

No recorded incident

6h 15m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for npm Registry. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

1 incident

Busiest day

6h 15m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

Not calculated: npm Registry is unknown, so there is no incident history to measure and no uptime figure is shown.

Other other services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedMedium

npm Registry: the vendor reports a partial disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

9/15/2026, 5:24:08 PM · 2h 2m

05:24 PM07:26 PM

Detection9/15/2026, 5:24:08 PM · 10d ago

Detected — medium severity

npm Registry: the vendor reports a partial disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

ResolvedMedium

npm Registry incident correlated across 1 signal group: official/vendor.

9/4/2026, 11:33:32 AM · 2h 23m

11:33 AM01:56 PM

Detection9/4/2026, 11:33:32 AM · 21d ago

Detected — medium severity

npm Registry incident correlated across 1 signal group: official/vendor.

ResolvedMedium

npm Registry incident correlated across 1 signal group: official/vendor.

9/3/2026, 9:54:01 PM · 1h 48m

09:54 PM11:42 PM

Detection9/3/2026, 9:54:01 PM · 21d ago

Detected — medium severity

npm Registry incident correlated across 1 signal group: official/vendor.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment npm Registry enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

0 reports aggregated in last 24h
Crowdsourced baseline detection
Official status page

Live signal

Status: Unknown
Monitoring: The vendor reports operational; no fresh independent reachability check confirms it.
Coverage: Verified against the vendor's own incident history
Reports (24h): 0
Baseline / hour: 5
Open threshold: 3x

Official site

www.npmjs.com

Related services

01.AI

Other

Unknown

1Password

Other

Normal

AI21 Studio

Other

Normal