Nager.Date vs Telegraph

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms58801
P95 · ms5533497
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no keyFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Nager.Date vs Telegraph: common questions

Which is more reliable, Nager.Date or Telegraph?

On our scheduled checks, Nager.Date leads on measured uptime — Nager.Date at 100% versus Telegraph at 99.02% 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 Telegraph?

Nager.Date has the lower median latency in our checks — Nager.Date responds in 58 ms versus Telegraph at 801 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 Telegraph need an API key?

Nager.Date needs no key, while Telegraph requires a free API key. If you want to start calling without signup, reach for Nager.Date first.

Can I call Nager.Date and Telegraph from the browser?

Yes — both Nager.Date and Telegraph 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 Telegraph free for commercial use?

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