Skip to contentAPILayer: production APIs with free plansExplore APILayer
FuelEconomy logo

Is FuelEconomy API down?

Current status, daily uptime history and troubleshooting for the FuelEconomy API (Vehicle).

No, FuelEconomy is up

FuelEconomy answered our last daily check (Nov 15, 2026, 13:58 UTC) in 1391 ms with HTTP 200.

Checking FuelEconomy now…

Sending a request from our server.

FuelEconomy API uptime history

30 days agoLatest check
Uptime
100% of 4 checks
Last check
Nov 15, 2026, 13:58 UTC
Response
1391 ms · HTTP 200
Last up
Now

We check FuelEconomy's listed URL (https://www.fueleconomy.gov/feg/ws/index.shtml) once a day. History started when FuelEconomy was first checked, so new entries show fewer than 30 days.

FuelEconomy API not working for you?

  1. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
  2. If calls fail only in the browser with a CORS error, FuelEconomy may not allow cross-origin requests. Call it from your server instead.
  3. If it works from one network but not another, check firewalls, VPNs and regional blocks.
  4. 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. 1BoltPatternHQ logo

    BoltPatternHQ API

    Online · 1007 ms

    Vehicle wheel fitment, bolt pattern (PCD), offset, and center bore specifications.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  2. 2ProblemsByVin logo

    ProblemsByVin API

    Online · 1062 ms

    Owner complaints, recalls and failure-mileage statistics by vehicle make, model and year.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  3. 3

    Decode US VINs offline from the NHTSA vPIC dataset, served from edge locations.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  4. 4Bike Reliability logo

    Bike Reliability API

    Online · 1888 ms

    UK motorcycle reliability ranked by first-time MOT pass rates.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  5. 5TransparentCars logo

    TransparentCars API

    Online · 1521 ms

    Fair-price valuation and yearly road tax (IUC) for used cars in Portugal.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS

Compare all FuelEconomy alternatives · APIs down right now

FuelEconomy API status FAQ

Is FuelEconomy API down right now?

FuelEconomy answered our last daily check (Nov 15, 2026, 13:58 UTC) in 1391 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether FuelEconomy is responding at this moment.

How do you check whether FuelEconomy API is up?

Once a day our checker requests FuelEconomy's listed URL (https://www.fueleconomy.gov/feg/ws/index.shtml) 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.

How reliable is FuelEconomy API?

FuelEconomy answered 100% of our last 4 daily checks. Above 99% is excellent for a free API; below 95% means you should cache responses and keep a fallback ready.

What can I use if FuelEconomy API is down?

Free Vehicle APIs that were up at their last check include BoltPatternHQ, ProblemsByVin, NHTSA Edge VIN Decoder. See the full list of FuelEconomy alternatives for a comparison.

Why does FuelEconomy 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, FuelEconomy 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.