Currents vs Gladia

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

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

Currents vs Gladia: common questions

Which is more reliable, Currents or Gladia?

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

Currents has the lower median latency in our checks — Currents responds in 586 ms versus Gladia at 1203 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 Currents and Gladia need an API key?

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

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

Are Currents and Gladia free for commercial use?

Currents has unclear commercial terms, and Gladia 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.