Gcore CDN vs Genderize.io

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

Uptime · 30d
Uptime · 90d100%41.2%
Uptime · 30d100%36.7%
P50 · ms362632
P95 · ms12211060
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionKeyless usage limited (x-rate-limit-limit: 25 observed); 2,500 names/mo with a free key
Rate limitUnpublishedKeyless cap 25 per x-rate-limit-limit header; remaining/reset exposed in response headers
In directory since2026-07-052026-07-05
operationalpartialdownno data

Gcore CDN vs Genderize.io: common questions

Which is more reliable, Gcore CDN or Genderize.io?

On our scheduled checks, Gcore CDN leads on measured uptime — Gcore CDN at 100% versus Genderize.io at 41.2% 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 Genderize.io?

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

Genderize.io needs no key, while Gcore CDN requires a free API key. If you want to start calling without signup, reach for Genderize.io first.

Can I call Gcore CDN and Genderize.io from the browser?

Yes — both Gcore CDN and Genderize.io 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 Gcore CDN and Genderize.io free for commercial use?

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