Is USTariffRates API down?
Current status, daily uptime history and troubleshooting for the USTariffRates API (Finance).
No, USTariffRates is up
USTariffRates answered our last daily check (Nov 15, 2026, 13:58 UTC) in 1650 ms with HTTP 200.
Checking USTariffRates now…
Sending a request from our server.
USTariffRates API uptime history
- Uptime
- 100% of 10 checks
- Last check
- Nov 15, 2026, 13:58 UTC
- Response
- 1650 ms · HTTP 200
- Last up
- Now
We check USTariffRates's listed URL (https://api.ustariffrates.com/openapi.json) once a day. History started when USTariffRates was first checked, so new entries show fewer than 30 days.
USTariffRates API not working for you?
- USTariffRates 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, USTariffRates 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.
Finance APIs up at their last check
- 1
Econdb API
Online · 691 msDownload economic and shipping data using Python.
- No API key needed
- 100% uptime (30 days)
- Returns JSON at its URL
- Callable from the browser (CORS)
No authHTTPSCORS - 2
Banking Access Index API
Online · 913 msWhich US business banking providers accept founders by country of residence, with sources.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 3
Brainy Prices API
Online · 903 msUAE living costs: KHDA fees, DLD rents, fuel, utilities, telecom and relocation, with dated sources.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 4
EstimateTax API
Online · 889 msUS federal, state and local income tax calculation for 2026, with the source of every figure.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 5
FloorGuard API
Online · 639 msSourced prop firm daily-loss and max-drawdown rules, plus a drawdown-room check.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS
Compare all USTariffRates alternatives · APIs down right now
USTariffRates API status FAQ
Is USTariffRates API down right now?
USTariffRates answered our last daily check (Nov 15, 2026, 13:58 UTC) in 1650 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether USTariffRates is responding at this moment.
How do you check whether USTariffRates API is up?
Once a day our checker requests USTariffRates's listed URL (https://api.ustariffrates.com/openapi.json) 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 USTariffRates API?
USTariffRates answered 100% of our last 10 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 USTariffRates API is down?
Free Finance APIs that were up at their last check include Econdb, Banking Access Index, Brainy Prices. See the full list of USTariffRates alternatives for a comparison.
Why does USTariffRates API work for others but not for me?
USTariffRates 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, USTariffRates may not allow cross-origin requests. Call it from your server instead.