Is NPPES API down?
Current status, daily uptime history and troubleshooting for the NPPES API (Health).
No, NPPES is up
NPPES answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1271 ms with HTTP 200.
Checking NPPES now…
Sending a request from our server.
NPPES API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- 1271 ms · HTTP 200
- Last up
- Now
We check NPPES's listed URL (https://npiregistry.cms.hhs.gov/registry/help-api) once a day. History started when NPPES was first checked, so new entries show fewer than 30 days.
NPPES API not working for you?
- A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
- If calls fail only in the browser with a CORS error, NPPES may not allow cross-origin requests. Call it from your server instead.
- If it works from one network but not another, check firewalls, VPNs and regional blocks.
- Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.
Health APIs up at their last check
- 1
FindSaunaPlunge API
Online · 502 msUS cold plunge and sauna venues with dated, source-quoted temperatures and prices.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 2
Longevity World Cup API
Online · 975 msPublic biological age competition data with biomarkers and rankings.
- No API key needed
- Returns JSON at its URL
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 3

Open Disease API
Online · 848 msAPI for Current cases and more stuff about COVID-19 and Influenza.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 4

Open Targets API
Online · 779 msGene-disease-drug target associations. A free health API by Open Targets Platform.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 5
Covid-19 Government Response API
Online · 1078 msGovernment measures tracker to fight against the Covid-19 pandemic.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS
NPPES API status FAQ
Is NPPES API down right now?
NPPES answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1271 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether NPPES is responding at this moment.
How do you check whether NPPES API is up?
Once a day our checker requests NPPES's listed URL (https://npiregistry.cms.hhs.gov/registry/help-api) and records whether it answers within 15 seconds. Answers like 401 (needs a key), 403 (blocks bots) or 429 (rate-limited) count as up, because the server responded. The listed URL is often the documentation page, so an API endpoint can occasionally fail while its docs stay up.
What can I use if NPPES API is down?
Free Health APIs that were up at their last check include FindSaunaPlunge, Longevity World Cup, Open Disease. See the full list of NPPES alternatives for a comparison.
Why does NPPES API work for others but not for me?
A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header. If calls fail only in the browser with a CORS error, NPPES may not allow cross-origin requests. Call it from your server instead. If it works from one network but not another, check firewalls, VPNs and regional blocks.