ipify vs Passantenfrequenzen Zürich

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms149569
P95 · ms3541228
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licensen/aUnverified
Free tierUnlimitedFree — limits not published
Rate limitNoneUnpublished
In directory since2026-05-022026-07-05
operationalpartialdownno data

ipify vs Passantenfrequenzen Zürich: common questions

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

On our scheduled checks, Passantenfrequenzen Zürich leads on measured uptime — ipify at 99.02% 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, ipify or Passantenfrequenzen Zürich?

ipify has the lower median latency in our checks — ipify responds in 149 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 ipify and Passantenfrequenzen Zürich need an API key?

Neither needs a paid key — ipify 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 ipify and Passantenfrequenzen Zürich from the browser?

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

ipify allows commercial use on its free tier, 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.