Is npm (npm Registry) down in Japan?
Vendor reports no incidentWhat npm (npm Registry) reports
npm (npm Registry) reports no incident on its status page.
As of the last successful poll, 2026-11-06 16:28 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingin Japan, measured from Tokyo
Our Tokyo probe last checked npm (npm Registry) at Nov 6, 2026, 4:12 PM UTC and read checks passing.
Over the last 24 hours we completed 59 checks from Tokyo and 59 answered cleanly, 100.00% availability.
Of the 9 other regions we check npm (npm Registry) from, all 9 read checks passing right now.
Email me when npm (npm Registry) reports an incident on its status page, and again when it reports it resolved.
What our Tokyo probe measured
Last checked Nov 6, 2026, 4:12 PM UTC.
npm (npm Registry) from Tokyo over the last 30 days
Over the last 30 days, npm (npm Registry) answered our Tokyo probe in 801 ms on average, and 1 check in 20 took longer than 1,164 ms.
Ranked by average response time across the 10 cities we check npm (npm Registry) from, Tokyo 8th; London was fastest at 454 ms and São Paulo slowest at 1,125 ms.
From Tokyo we ran 3,918 checks of npm (npm Registry) in 30 days, and 3,908 answered cleanly: 99.74% availability.
4 of the 30 days had at least one failed check. The weakest was Oct 27 (UTC), at 96.47% across 142 checks.
In Tokyo local time (GMT+9), npm (npm Registry) was slowest around 4 PM, at 1,465 ms on average over the last 14 days, and quickest around 1 PM, at 944 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Fri, Nov 6 | 39 | 100.00% | 1,180 ms |
| Thu, Nov 5 | 61 | 100.00% | 1,259 ms |
| Wed, Nov 4 | 58 | 100.00% | 958 ms |
| Tue, Nov 3 | 60 | 100.00% | 1,113 ms |
| Mon, Nov 2 | 111 | 100.00% | 1,162 ms |
| Sun, Nov 1 | 144 | 100.00% | 1,094 ms |
| Sat, Oct 31 | 143 | 100.00% | 1,007 ms |
| Fri, Oct 30 | 143 | 100.00% | 1,171 ms |
| Thu, Oct 29 | 144 | 100.00% | 1,144 ms |
| Wed, Oct 28 | 143 | 99.30% | 921 ms |
| Tue, Oct 27 | 142 | 96.47% | 1,236 ms |
| Mon, Oct 26 | 143 | 98.60% | 1,144 ms |
| Sun, Oct 25 | 144 | 100.00% | 976 ms |
| Sat, Oct 24 | 142 | 98.59% | 1,209 ms |
npm (npm Registry) outages measured from Japan
Our Tokyo probe measured no confirmed npm (npm Registry) outage in the last 90 days.
How the other regions read right now
Of the 9 other regions we check npm (npm Registry) from, all 9 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Ashburn | Checks passing | 100.00% of 142 checks |
| San Jose | Checks passing | 100.00% of 110 checks |
| Frankfurt | Checks passing | 100.00% of 99 checks |
| Chicago | Checks passing | 100.00% of 72 checks |
| Toronto | Checks passing | 100.00% of 72 checks |
| London | Checks passing | 100.00% of 72 checks |
| Singapore | Checks passing | 100.00% of 71 checks |
| Sydney | Checks passing | 100.00% of 72 checks |
| São Paulo | Checks passing | 100.00% of 72 checks |
Other countries we check npm (npm Registry) from
How we measured this
Japan readings on this page come from RealUptime's own Tokyo probe against npm (npm Registry)'s public endpoints. They are not user reports, and they are not npm (npm Registry)'s own status page.
See npm (npm Registry)'s full check readings, the 90-day history by region, or the outage tracker methodology.
Check your own site from Tokyo
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter