OkSurf vs Voidly

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms6241238
P95 · ms18703894
Authnonenone
CORSnoyes
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

OkSurf vs Voidly: common questions

Which is more reliable, OkSurf or Voidly?

Both are neck-and-neck — OkSurf and Voidly 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, OkSurf or Voidly?

OkSurf has the lower median latency in our checks — OkSurf responds in 624 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 OkSurf and Voidly need an API key?

Neither needs a paid key — OkSurf 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 OkSurf and Voidly from the browser?

Only Voidly is browser-friendly — it returns CORS headers over HTTPS. OkSurf needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are OkSurf and Voidly free for commercial use?

OkSurf 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.