Is Numverify API down?
Current status, daily uptime history and troubleshooting for the Numverify API (Phone).
No, Numverify is up
Numverify answered our last daily check (Oct 24, 2026, 12:25 UTC) in 894 ms with HTTP 200.
Checking Numverify now…
Sending a request from our server.
Numverify API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- 894 ms · HTTP 200
- Last up
- Now
We check Numverify's listed URL (https://numverify.com?utm_source=Github&utm_medium=Referral&utm_campaign=Public-apis-repo-Best-sellers) once a day. History started when Numverify was first checked, so new entries show fewer than 30 days.
Numverify API not working for you?
- Numverify needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string.
- 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, Numverify 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.
Phone APIs up at their last check
- 1
Phone Specification API
Online · 795 msRest Api for Phone specifications.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 2
Veriphone API
Online · 54 msPhone number validation & carrier lookup.
- Fast: 54 ms response
- Callable from the browser (CORS)
- HTTPS
apiKeyHTTPSCORS - 3
Cloudmersive Validate API
Online · 847 msValidate international phone numbers. A free phone API by Cloudmersive.
- Callable from the browser (CORS)
- HTTPS
apiKeyHTTPSCORS - 4
Phone Validation API
Online · 2411 msValidate any phone number in real time and get its carrier, line type, and location.
- Callable from the browser (CORS)
- HTTPS
apiKeyHTTPSCORS - 5
Numlookup API
Online · 495 msPhone number validation and carrier lookup API with global coverage.
- HTTPS
apiKeyHTTPSCORS ?
Numverify API status FAQ
Is Numverify API down right now?
Numverify answered our last daily check (Oct 24, 2026, 12:25 UTC) in 894 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether Numverify is responding at this moment.
How do you check whether Numverify API is up?
Once a day our checker requests Numverify's listed URL (https://numverify.com?utm_source=Github&utm_medium=Referral&utm_campaign=Public-apis-repo-Best-sellers) 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 Numverify API is down?
Free Phone APIs that were up at their last check include Phone Specification, Veriphone, Cloudmersive Validate. See the full list of Numverify alternatives for a comparison.
Why does Numverify API work for others but not for me?
Numverify needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string. 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, Numverify may not allow cross-origin requests. Call it from your server instead.