Passantenfrequenzen Zürich vs PyPI

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms56946
P95 · ms1228446
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Passantenfrequenzen Zürich vs PyPI: common questions

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

Both are neck-and-neck — Passantenfrequenzen Zürich and PyPI each measure 100% 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, Passantenfrequenzen Zürich or PyPI?

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

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

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

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

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