Is NHTSA API down?
Current status, daily uptime history and troubleshooting for the NHTSA API (Vehicle).
No, NHTSA is up
NHTSA answered our last daily check (Oct 24, 2026, 12:25 UTC) in 704 ms with HTTP 200.
Checking NHTSA now…
Sending a request from our server.
NHTSA API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- 704 ms · HTTP 200
- Last up
- Now
We check NHTSA's listed URL (https://vpic.nhtsa.dot.gov/api/) once a day. History started when NHTSA was first checked, so new entries show fewer than 30 days.
NHTSA 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, NHTSA 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.
Vehicle APIs up at their last check
- 1
Bike Reliability API
Online · 524 msUK motorcycle reliability ranked by first-time MOT pass rates.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 2

ProblemsByVin API
Online · 523 msOwner complaints, recalls and failure-mileage statistics by vehicle make, model and year.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 3

TransparentCars API
Online · 644 msFair-price valuation and yearly road tax (IUC) for used cars in Portugal.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 4

Brazilian Vehicles and Prices API
Online · 312 msVehicles information from Fundação Instituto de Pesquisas Econômicas - Fipe.
- No API key needed
- Fast: 312 ms response
- HTTPS
No authHTTPSNo CORS - 5

CarVector API
Online · 1152 msVehicle specs, images, recalls, and DTC codes across 1925-2029.
- Callable from the browser (CORS)
- HTTPS
apiKeyHTTPSCORS
NHTSA API status FAQ
Is NHTSA API down right now?
NHTSA answered our last daily check (Oct 24, 2026, 12:25 UTC) in 704 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether NHTSA is responding at this moment.
How do you check whether NHTSA API is up?
Once a day our checker requests NHTSA's listed URL (https://vpic.nhtsa.dot.gov/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 NHTSA API is down?
Free Vehicle APIs that were up at their last check include Bike Reliability, ProblemsByVin, TransparentCars. See the full list of NHTSA alternatives for a comparison.
Why does NHTSA 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, NHTSA 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.