Skip to content
Exchangerate.host logo

Is Exchangerate.host API down?

Current status, daily uptime history and troubleshooting for the Exchangerate.host API (Currency Exchange).

No, Exchangerate.host is up

Exchangerate.host answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1177 ms with HTTP 200.

Checking Exchangerate.host now…

Sending a request from our server.

Exchangerate.host API uptime history

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

We check Exchangerate.host's listed URL (https://exchangerate.host?utm_source=Github&utm_medium=Referral&utm_campaign=Public-apis-repo-Best-sellers) once a day. History started when Exchangerate.host was first checked, so new entries show fewer than 30 days.

Exchangerate.host API not working for you?

  1. Exchangerate.host 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, Exchangerate.host 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.

Currency Exchange APIs up at their last check

  1. 1Currency-api logo

    Currency-api

    Online · 712 ms

    Free Currency Exchange Rates API with 150+ Currencies & No Rate Limits.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  2. 2Daleelak logo

    Daleelak API

    Online · 512 ms

    Egyptian bank and dealer exchange rates, gold and silver prices.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  3. 3Fulusly logo

    Fulusly API

    Online · 486 ms

    Exchange rates for 144 currencies with daily history back to the 1990s, English and Arabic.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  4. 4National Bank of Poland logo

    A collection of currency exchange rates (data in XML and JSON).

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  5. 5paralelo.bo logo

    paralelo.bo API

    Online · 524 ms

    Bolivia parallel-market USD/BOB exchange rate, aggregated from P2P sources every 60s.

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

Compare all Exchangerate.host alternatives · APIs down right now

Exchangerate.host API status FAQ

Is Exchangerate.host API down right now?

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

How do you check whether Exchangerate.host API is up?

Once a day our checker requests Exchangerate.host's listed URL (https://exchangerate.host?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 Exchangerate.host API is down?

Free Currency Exchange APIs that were up at their last check include Currency-api, Daleelak, Fulusly. See the full list of Exchangerate.host alternatives for a comparison.

Why does Exchangerate.host API work for others but not for me?

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