University of Oslo vs Zenodo

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

Uptime · 30d
Uptime · 90d98.0%99.02%
Uptime · 30d100%100%
P50 · ms17631698
P95 · ms49604935
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished30 req/window · 29 remaining · resets 1783516620
In directory since2026-07-052026-07-05
operationalpartialdownno data

University of Oslo vs Zenodo: common questions

Which is more reliable, University of Oslo or Zenodo?

On our scheduled checks, Zenodo leads on measured uptime — University of Oslo at 98.0% versus Zenodo at 99.02% 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, University of Oslo or Zenodo?

Zenodo has the lower median latency in our checks — University of Oslo responds in 1763 ms versus Zenodo at 1698 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 University of Oslo and Zenodo need an API key?

Neither needs a paid key — University of Oslo is callable with no signup, and Zenodo is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call University of Oslo and Zenodo from the browser?

Yes — both University of Oslo and Zenodo 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 University of Oslo and Zenodo free for commercial use?

University of Oslo has unclear commercial terms, and Zenodo 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.