shipapis
StarSubmit an APISubmit API

Nager.Date vs Public Time API

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

APINager.DateHEALTHY100Public Time APIHEALTHY97
Uptime · 30d
Uptime · 90d100%99.44%
Uptime · 30d100%98.3%
P50 · ms51311
P95 · ms553449
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no keyFree — limits not published
Rate limitUnpublishedRetry-After: 1020s
In directory since2026-07-052026-07-05
operationalpartialdownno data

Nager.Date vs Public Time API: common questions

Which is more reliable, Nager.Date or Public Time API?

On our scheduled checks, Nager.Date leads on measured uptime — Nager.Date at 100% versus Public Time API at 99.44% 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, Nager.Date or Public Time API?

Nager.Date has the lower median latency in our checks — Nager.Date responds in 51 ms versus Public Time API at 311 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 Nager.Date and Public Time API need an API key?

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

Can I call Nager.Date and Public Time API from the browser?

Only Nager.Date 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 Nager.Date and Public Time API free for commercial use?

Nager.Date has unclear commercial terms, and Public Time API 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.