Is Transport for Germany API down?
Current status, daily uptime history and troubleshooting for the Transport for Germany API (Transportation).
Possibly: Transport for Germany's last check failed
Our latest daily check of Transport for Germany (Oct 24, 2026, 12:25 UTC) failed: it didn't answer in time. One failure can be a blip; the live check below tells you whether it's still failing.
Checking Transport for Germany now…
Sending a request from our server.
Transport for Germany API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- It didn't answer in time
- Last up
- Not seen up yet
We check Transport for Germany's listed URL (http://data.deutschebahn.com/dataset/api-fahrplan) once a day. History started when Transport for Germany was first checked, so new entries show fewer than 30 days.
Transport for Germany API not working for you?
- Transport for Germany 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, Transport for Germany may not allow cross-origin requests. Call it from your server instead.
- Transport for Germany is listed without HTTPS. Browsers block plain-HTTP requests from HTTPS pages (mixed content).
- 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
Compare all Transport for Germany alternatives · APIs down right now
Transport for Germany API status FAQ
Is Transport for Germany API down right now?
Our latest daily check of Transport for Germany (Oct 24, 2026, 12:25 UTC) failed: it didn't answer in time. One failure can be a blip; the live check below tells you whether it's still failing. This page also runs a live check from our server when you open it, so you can see whether Transport for Germany is responding at this moment.
How do you check whether Transport for Germany API is up?
Once a day our checker requests Transport for Germany's listed URL (http://data.deutschebahn.com/dataset/api-fahrplan) 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 Transport for Germany 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 Transport for Germany alternatives for a comparison.
Why does Transport for Germany API work for others but not for me?
Transport for Germany 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, Transport for Germany may not allow cross-origin requests. Call it from your server instead.