shipapis
StarSubmit an APISubmit API

Public Time API vs TimeAPI.io

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

APIPublic Time APIHEALTHY98TimeAPI.ioHEALTHY87
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms2421040
P95 · ms3823967
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Public Time API vs TimeAPI.io: common questions

Which is more reliable, Public Time API or TimeAPI.io?

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

Public Time API has the lower median latency in our checks — Public Time API responds in 242 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 Public Time API and TimeAPI.io need an API key?

Neither needs a paid key — Public Time API is callable with no signup, and TimeAPI.io is callable with no signup. Both are quick to prototype with; rate limits still apply.

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

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

Are Public Time API and TimeAPI.io free for commercial use?

Public Time 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.