Nager.Date vs PostStack

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree, no keyFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Nager.Date vs PostStack: common questions

Which is more reliable, Nager.Date or PostStack?

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

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

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

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

Are Nager.Date and PostStack free for commercial use?

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