Keen IO vs Open Notify

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

Uptime · 30d
Uptime · 90d100%71.6%
Uptime · 30d100%65.0%
P50 · ms667241
P95 · ms14614298
AuthapiKeynone
CORSnoyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedn/a
Free tierFree tier — key may be requiredUnlimited (volunteer-run)
Rate limitUnpublishedPlease be gentle
In directory since2026-07-052026-05-02
operationalpartialdownno data

Keen IO vs Open Notify: common questions

Which is more reliable, Keen IO or Open Notify?

On our scheduled checks, Keen IO leads on measured uptime — Keen IO at 100% versus Open Notify at 71.6% 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, Keen IO or Open Notify?

Open Notify has the lower median latency in our checks — Keen IO responds in 667 ms versus Open Notify at 241 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 Keen IO and Open Notify need an API key?

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

Can I call Keen IO and Open Notify from the browser?

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

Are Keen IO and Open Notify free for commercial use?

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