IPinfo vs Passantenfrequenzen Zürich

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

Uptime · 30d
Uptime · 90d94.1%100%
Uptime · 30d90.0%100%
P50 · ms200569
P95 · ms4731228
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierKeyless /json works with limits; free token recommended (IPinfo Lite offers higher/unlimited access with a token)Free — limits not published
Rate limitKeyless/unauthenticated access is rate-limited; numeric caps not stated on the developers pageUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

IPinfo vs Passantenfrequenzen Zürich: common questions

Which is more reliable, IPinfo or Passantenfrequenzen Zürich?

On our scheduled checks, Passantenfrequenzen Zürich leads on measured uptime — IPinfo at 94.1% versus Passantenfrequenzen Zürich at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, IPinfo or Passantenfrequenzen Zürich?

IPinfo has the lower median latency in our checks — IPinfo responds in 200 ms versus Passantenfrequenzen Zürich at 569 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 IPinfo and Passantenfrequenzen Zürich need an API key?

Neither needs a paid key — IPinfo is callable with no signup, and Passantenfrequenzen Zürich is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call IPinfo and Passantenfrequenzen Zürich from the browser?

Yes — both IPinfo and Passantenfrequenzen Zürich 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 IPinfo and Passantenfrequenzen Zürich free for commercial use?

IPinfo has unclear commercial terms, and Passantenfrequenzen Zürich 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.