Skip to content
FDA Recalls logo

Is FDA Recalls API down?

Current status, daily uptime history and troubleshooting for the FDA Recalls API (Health).

No, FDA Recalls is up

FDA Recalls answered our last daily check (Oct 24, 2026, 12:25 UTC) in 433 ms with HTTP 200.

Checking FDA Recalls now…

Sending a request from our server.

FDA Recalls API uptime history

30 days agoLatest check
Uptime
2 checks so far
Last check
Oct 24, 2026, 12:25 UTC
Response
433 ms · HTTP 200
Last up
Now

We check FDA Recalls's listed URL (https://rapidapi.com/crisp-point-studio-crisp-point-studio-default/api/live-fda-product-food-recalls) once a day. History started when FDA Recalls was first checked, so new entries show fewer than 30 days.

FDA Recalls API not working for you?

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

    FindSaunaPlunge API

    Online · 502 ms

    US 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. 2Longevity World Cup logo

    Longevity World Cup API

    Online · 975 ms

    Public 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. 3Open Disease logo

    Open Disease API

    Online · 848 ms

    API for Current cases and more stuff about COVID-19 and Influenza.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  4. 4Open Targets logo

    Open Targets API

    Online · 779 ms

    Gene-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. 5Covid-19 Government Response logo

    Government measures tracker to fight against the Covid-19 pandemic.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS

Compare all FDA Recalls alternatives · APIs down right now

FDA Recalls API status FAQ

Is FDA Recalls API down right now?

FDA Recalls answered our last daily check (Oct 24, 2026, 12:25 UTC) in 433 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether FDA Recalls is responding at this moment.

How do you check whether FDA Recalls API is up?

Once a day our checker requests FDA Recalls's listed URL (https://rapidapi.com/crisp-point-studio-crisp-point-studio-default/api/live-fda-product-food-recalls) 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 FDA Recalls 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 FDA Recalls alternatives for a comparison.

Why does FDA Recalls API work for others but not for me?

FDA Recalls 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, FDA Recalls may not allow cross-origin requests. Call it from your server instead.