University of Oslo vs Voidly

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

Uptime · 30d
Uptime · 90d98.0%100%
Uptime · 30d100%100%
P50 · ms17631238
P95 · ms49603894
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY 4.0
Free tierFree — limits not publishedFree (keyless data endpoints; Hydra ML endpoints need a key)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

University of Oslo vs Voidly: common questions

Which is more reliable, University of Oslo or Voidly?

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

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

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

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

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

University of Oslo has unclear commercial terms, and Voidly allows commercial use on its free tier. 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.