Currents vs Noozra

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

Uptime · 30d
Uptime · 90d100%80.9%
Uptime · 30d100%41.4%
P50 · ms291289
P95 · ms1165945
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (aggregated RSS headlines)
Free tierFree tier — key may be requiredFree tier available (pricing tiers published at /api/pricing)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Currents vs Noozra: common questions

Which is more reliable, Currents or Noozra?

On our scheduled checks, Currents leads on measured uptime — Currents at 100% versus Noozra at 80.9% 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, Currents or Noozra?

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

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

Can I call Currents and Noozra from the browser?

Only Noozra 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 Noozra free for commercial use?

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