Is AZ511 API down?
Current status, daily uptime history and troubleshooting for the AZ511 API (Transportation).
No, AZ511 is up
AZ511 answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1129 ms with HTTP 200.
Checking AZ511 now…
Sending a request from our server.
AZ511 API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- 1129 ms · HTTP 200
- Last up
- Now
We check AZ511's listed URL (https://www.az511.com/developers/doc) once a day. History started when AZ511 was first checked, so new entries show fewer than 30 days.
AZ511 API not working for you?
- AZ511 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, AZ511 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.
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
AZ511 API status FAQ
Is AZ511 API down right now?
AZ511 answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1129 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether AZ511 is responding at this moment.
How do you check whether AZ511 API is up?
Once a day our checker requests AZ511's listed URL (https://www.az511.com/developers/doc) 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 AZ511 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 AZ511 alternatives for a comparison.
Why does AZ511 API work for others but not for me?
AZ511 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, AZ511 may not allow cross-origin requests. Call it from your server instead.