npm logo
ALL SYSTEMS OPERATIONAL

npm systems
are operational.

Pulsetic detects outages before the provider officially reports them. Monitoring since Sep 2023 · 54 incidents caught

Last checked: just now · 0 user reports (24h) · Trusted by 30,000+ teams

  • ALL SYSTEMS OPERATIONAL

    npm is up and running.

    Last incident resolved 4 weeks ago


    No active incidents at this time. Noticed something?
  • User Reports: Last 24 Hours

    0 reports

    Bars represent 20-min intervals. Occasional spikes may reflect individual issues, not widespread outages.

  • Outage Map

    No reports yet

    Reports by region (last 24h)

    No reports in the last 24h
  • Recent User Reports

    Live

    Latest 50 reports from the last 48 hours

You checked npm. Who checks your website?

Pulsetic is website uptime monitoring. Add a website you own and it gets checked as often as every 30 seconds, so the next answer arrives by email.

10 monitors free, email alerts on failure and recovery. No credit card.

  • Top reported issues

    Click an issue to upvote it and help us better indicate the service status.

    Service outage 0
    Degraded performance 0
    Error messages 0
    Timeouts / no response 0
    Authentication issues 0
    Network / connectivity issues 0
    Feature not working 0
    API errors 0
    Billing or usage issues 0
    Other 0

    Have a different problem?

  • Issue breakdown

    0 total votes

    Distribution of reported issues over the last 24 hours.

    Service outage 0%
    Degraded performance 0%
    Error messages 0%
    Timeouts / no response 0%
    Authentication issues 0%
    Network / connectivity issues 0%
    Feature not working 0%
    API errors 0%
    Billing or usage issues 0%
    Other 0%

Last 90 days

90-Day Health Summary

  • Total Incidents

    4

    Since Sep 2023

  • Major / Critical

    1

    1 high-impact incident

  • Minor Incidents

    3

    Avg. 0.0 per day

  • Median Resolution

    2h 15m

    P95: 4h 23m

From official status page

Recent Outage History

View all incidents →
Incident Started Duration Impact Status Link
intermittent Publish Failures
Jul 30, 2026 · 12:06 PM 4h 23m
Minor
Resolved
Details →
Publish and Install failures
Jul 24, 2026 · 11:08 AM 30m
Major
Resolved
Details →
intermittent Publish and Install Failures
Jul 23, 2026 · 4:09 PM 3h 42m
Minor
Resolved
Details →
intermittent Publish Failures
Jun 12, 2026 · 12:08 PM 48m
Minor
Resolved
Details →
npm website issues
Apr 29, 2026 · 8:07 PM 42m
Minor
Resolved
Details →
Degraded Performance in View Package and Login on npmjs.com
Apr 29, 2026 · 4:48 PM 2h 47m
Minor
Resolved
Details →
npm website degraded service
Apr 28, 2026 · 7:55 PM 2h 29m
Minor
Resolved
Details →
npm Website is unavailable
Apr 27, 2026 · 9:06 PM 1h 24m
Critical
Resolved
Details →
Increased errors in viewing packages and authentication on npmjs.com
Apr 1, 2026 · 10:05 AM 3h 6m
None
Resolved
Details →
Degraded Performance in View Package and Login on npmjs.com
Mar 31, 2026 · 7:12 PM 2h 36m
Minor
Resolved
Details →

Common questions

Frequently Asked Questions

  • Is npm down today?

    Check the status badge at the top of this page for the current status. Pulsetic polls the official status page every few minutes and cross-references with user reports to give you the most accurate picture.

  • How often does npm go down?

    Based on our 90-day data, we've detected 4 incidents, of which 1 were major or critical. The median resolution time is 2h 15m.

  • How are outages detected?

    Pulsetic polls the official status page every few minutes from multiple global locations. Crowdsourced user reports provide an additional early-warning signal, often surfacing issues before the official monitors catch them.

  • Is it down for everyone or just me?

    The outage map and region breakdown help answer this. If reports are concentrated in one area it may be regional; if hotspots appear globally it's a widespread outage. Submit your own report to help others understand the scope.

  • What does "never acknowledged" mean?

    "Never acknowledged" means Pulsetic detected a real service disruption, confirmed by multiple user reports, but the official status page never posted an incident for it. This is one of the core reasons teams use third-party monitoring alongside official status pages.