Nexmo API vs TimeAPI.io

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms5671040
P95 · ms12213967
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limit10, 120;w=60;name="crd|generic_key^nexmo-gloo.sanity-service-remote-address-120-rpm|remote_address", 10;w=1;name="crd|generic_key^nexmo-gloo.sanity-service-remote-address-10-rps|remote_address" req/window · 9 remaining · resets 1Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Nexmo API vs TimeAPI.io: common questions

Which is more reliable, Nexmo API or TimeAPI.io?

Both are neck-and-neck — Nexmo API and TimeAPI.io 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, Nexmo API or TimeAPI.io?

Nexmo API has the lower median latency in our checks — Nexmo API responds in 567 ms versus TimeAPI.io at 1040 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 Nexmo API and TimeAPI.io need an API key?

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

Can I call Nexmo API and TimeAPI.io from the browser?

Only TimeAPI.io is browser-friendly — it returns CORS headers over HTTPS. Nexmo API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Nexmo API and TimeAPI.io free for commercial use?

Nexmo API has unclear commercial terms, and TimeAPI.io 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.