Gcore CDN vs Hunter

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms362362
P95 · ms1221859
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Gcore CDN vs Hunter: common questions

Which is more reliable, Gcore CDN or Hunter?

Both are neck-and-neck — Gcore CDN and Hunter 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, Gcore CDN or Hunter?

They're evenly matched on speed — both Gcore CDN and Hunter post a 362 ms median (P50) in our checks. Look at the P95 row above if worst-case latency matters more than the typical response for your use case.

Do Gcore CDN and Hunter need an API key?

Both ask you to authenticate — Gcore CDN uses an API key and Hunter uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Gcore CDN and Hunter from the browser?

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

Are Gcore CDN and Hunter free for commercial use?

Gcore CDN has unclear commercial terms, and Hunter 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.