shipapis
StarSubmit an APISubmit API

Gcore CDN vs VerifyEd

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

APIGcore CDNHEALTHY96VerifyEdHEALTHY76
Uptime · 30d
Uptime · 90d100%97.1%
Uptime · 30d100%95.0%
P50 · ms3621933
P95 · ms12213606
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree tier — API key required
Rate limitUnpublished100 req/window · 99 remaining · resets 1783522020
In directory since2026-07-052026-07-05
operationalpartialdownno data

Gcore CDN vs VerifyEd: common questions

Which is more reliable, Gcore CDN or VerifyEd?

On our scheduled checks, Gcore CDN leads on measured uptime — Gcore CDN at 100% versus VerifyEd at 97.1% 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, Gcore CDN or VerifyEd?

Gcore CDN has the lower median latency in our checks — Gcore CDN responds in 362 ms versus VerifyEd at 1933 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 Gcore CDN and VerifyEd need an API key?

Both ask you to authenticate — Gcore CDN uses an API key and VerifyEd 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 VerifyEd from the browser?

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

Are Gcore CDN and VerifyEd free for commercial use?

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