Transport for London, England vs Transport for Switzerland

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (powered by Opendata.ch)
Free tierFree tier — API key may be required for productionFree — no key required
Rate limitUnpublishedBounded by timetable.search.ch limits (no fixed number published)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Transport for London, England vs Transport for Switzerland: common questions

Which is more reliable, Transport for London, England or Transport for Switzerland?

On our scheduled checks, Transport for Switzerland leads on measured uptime — Transport for London, England at —% versus Transport for Switzerland at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Transport for London, England and Transport for Switzerland need an API key?

Transport for Switzerland needs no key, while Transport for London, England requires a free API key. If you want to start calling without signup, reach for Transport for Switzerland first.

Can I call Transport for London, England and Transport for Switzerland from the browser?

Yes — both Transport for London, England and Transport for Switzerland send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Transport for London, England and Transport for Switzerland free for commercial use?

Transport for London, England has unclear commercial terms, and Transport for Switzerland has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.