Nager.Date vs TimeZones iCal Library

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no keyFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Nager.Date vs TimeZones iCal Library: common questions

Which is more reliable, Nager.Date or TimeZones iCal Library?

On our scheduled checks, TimeZones iCal Library leads on measured uptime — Nager.Date at —% versus TimeZones iCal Library 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 Nager.Date and TimeZones iCal Library need an API key?

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

Can I call Nager.Date and TimeZones iCal Library from the browser?

Yes — both Nager.Date and TimeZones iCal Library send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Nager.Date and TimeZones iCal Library free for commercial use?

Nager.Date has unclear commercial terms, and TimeZones iCal Library 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.