Open Notify vs Replicate

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesno
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licensen/aUnverified
Free tierUnlimited (volunteer-run)Free tier — API key required
Rate limitPlease be gentleUnpublished
In directory since2026-05-022026-07-05
operationalpartialdownno data

Open Notify vs Replicate: common questions

Which is more reliable, Open Notify or Replicate?

On our scheduled checks, Replicate leads on measured uptime — Open Notify at —% versus Replicate 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 Open Notify and Replicate need an API key?

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

Can I call Open Notify and Replicate from the browser?

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

Are Open Notify and Replicate free for commercial use?

Open Notify has unclear commercial terms, and Replicate 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.