PostStack vs Public Time API

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms1066242
P95 · ms1890382
AuthapiKeynone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

PostStack vs Public Time API: common questions

Which is more reliable, PostStack or Public Time API?

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

Public Time API has the lower median latency in our checks — PostStack responds in 1066 ms versus Public Time API at 242 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 PostStack and Public Time API need an API key?

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

Can I call PostStack and Public Time API from the browser?

Neither sends browser-friendly CORS headers reliably, so call PostStack and Public Time API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are PostStack and Public Time API free for commercial use?

PostStack 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.