Skip to content
Humanitarian Data Exchange logo

Is Humanitarian Data Exchange API down?

Current status, daily uptime history and troubleshooting for the Humanitarian Data Exchange API (Health).

No, Humanitarian Data Exchange is up

Humanitarian Data Exchange answered our last daily check (Oct 24, 2026, 12:25 UTC) in 726 ms with HTTP 406.

Checking Humanitarian Data Exchange now…

Sending a request from our server.

Humanitarian Data Exchange API uptime history

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

We check Humanitarian Data Exchange's listed URL (https://data.humdata.org/) once a day. History started when Humanitarian Data Exchange was first checked, so new entries show fewer than 30 days.

What does HTTP 406 mean? Read the 406 explainer.

Humanitarian Data Exchange 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, Humanitarian Data Exchange 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.

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 Humanitarian Data Exchange alternatives · APIs down right now

Humanitarian Data Exchange API status FAQ

Is Humanitarian Data Exchange API down right now?

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

How do you check whether Humanitarian Data Exchange API is up?

Once a day our checker requests Humanitarian Data Exchange's listed URL (https://data.humdata.org/) 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 Humanitarian Data Exchange 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 Humanitarian Data Exchange alternatives for a comparison.

Why does Humanitarian Data Exchange 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, Humanitarian Data Exchange 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.