Transport for Switzerland vs Transport for United States

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (powered by Opendata.ch)Data copyright transit agencies / Umo IQ
Free tierFree — no key requiredFree — limits not published
Rate limitBounded by timetable.search.ch limits (no fixed number published)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Transport for Switzerland vs Transport for United States: common questions

Which is more reliable, Transport for Switzerland or Transport for United States?

On our scheduled checks, Transport for United States leads on measured uptime — Transport for Switzerland at —% versus Transport for United States 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 Switzerland and Transport for United States need an API key?

Neither needs a paid key — Transport for Switzerland is callable with no signup, and Transport for United States is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Transport for Switzerland and Transport for United States from the browser?

Yes — both Transport for Switzerland and Transport for United States 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 Switzerland and Transport for United States free for commercial use?

Transport for Switzerland has unclear commercial terms, and Transport for United States 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.