Currents vs Sofiaplan

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms5861666
P95 · ms11653475
AuthapiKeynone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Currents vs Sofiaplan: common questions

Which is more reliable, Currents or Sofiaplan?

Both are neck-and-neck — Currents and Sofiaplan 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 Sofiaplan?

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

Sofiaplan needs no key, while Currents requires a free API key. If you want to start calling without signup, reach for Sofiaplan first.

Can I call Currents and Sofiaplan from the browser?

Neither sends browser-friendly CORS headers reliably, so call Currents and Sofiaplan from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Currents and Sofiaplan free for commercial use?

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