Currents vs New York Times

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree tier — 500 requests/day
Rate limitUnpublished500 requests/day on free plan
In directory since2026-07-052026-07-05
operationalpartialdownno data

Currents vs New York Times: common questions

Which is more reliable, Currents or New York Times?

On our scheduled checks, New York Times leads on measured uptime — Currents at —% versus New York Times at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Currents and New York Times need an API key?

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

Only New York Times 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 New York Times free for commercial use?

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