SBB Open Data vs Transport for The Netherlands
Same instrument, two spec sheets — measured, not claimed.
SBB Open Data vs Transport for The Netherlands: common questions
Which is more reliable, SBB Open Data or Transport for The Netherlands?
Both are neck-and-neck — SBB Open Data and Transport for The Netherlands each measure 99.02% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.
Which is faster, SBB Open Data or Transport for The Netherlands?
Transport for The Netherlands has the lower median latency in our checks — SBB Open Data responds in 1230 ms versus Transport for The Netherlands at 680 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.
Do SBB Open Data and Transport for The Netherlands need an API key?
Neither needs a paid key — SBB Open Data is callable with no signup, and Transport for The Netherlands is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call SBB Open Data and Transport for The Netherlands from the browser?
Neither sends browser-friendly CORS headers reliably, so call SBB Open Data and Transport for The Netherlands from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.
Are SBB Open Data and Transport for The Netherlands free for commercial use?
SBB Open Data has unclear commercial terms, and Transport for The Netherlands 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.