Is On va où ? API down?
Current status, daily uptime history and troubleshooting for the On va où ? API (Transportation).
No, On va où ? is up
On va où ? answered our last daily check (Oct 24, 2026, 12:25 UTC) in 757 ms with HTTP 200.
Checking On va où ? now…
Sending a request from our server.
On va où ? API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- 757 ms · HTTP 200
- Last up
- Now
We check On va où ?'s listed URL (https://onvaou.app/developers/routing-api.html) once a day. History started when On va où ? was first checked, so new entries show fewer than 30 days.
On va où ? API not working for you?
- On va où ? 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.
- On va où ? doesn't send CORS headers, so browsers block calls made directly from a web page. 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.
Transportation APIs up at their last check
- 1
AirportMiles API
Online · 748 msAirport codes, distances, routes and passenger numbers as static JSON files.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 2
Aviation Safety Data API
Online · 700 ms164,068 aircraft accident narratives from 128 official investigation authorities, plus FAA data.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 3
Can I enter API
Online · 521 msVisa and entry requirements for 199 passports, cited to official sources, verified daily.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 4
ConnectMeGuru API
Online · 793 msSearch and purchase prepaid travel eSIM data plans across 190+ countries.
- No API key needed
- Returns JSON at its URL
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 5
GTFS Scorecard API
Online · 1021 msData-quality grades and prioritized fixes for 2,400+ public transit GTFS feed records.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS
On va où ? API status FAQ
Is On va où ? API down right now?
On va où ? answered our last daily check (Oct 24, 2026, 12:25 UTC) in 757 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether On va où ? is responding at this moment.
How do you check whether On va où ? API is up?
Once a day our checker requests On va où ?'s listed URL (https://onvaou.app/developers/routing-api.html) 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 On va où ? API is down?
Free Transportation APIs that were up at their last check include AirportMiles, Aviation Safety Data, Can I enter. See the full list of On va où ? alternatives for a comparison.
Why does On va où ? API work for others but not for me?
On va où ? 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. On va où ? doesn't send CORS headers, so browsers block calls made directly from a web page. Call it from your server instead.