Public Time API vs Webex

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

Uptime · 30d
Uptime · 90d99.44%100%
Uptime · 30d98.3%100%
P50 · ms311685
P95 · ms4491323
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitRetry-After: 1020sUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Public Time API vs Webex: common questions

Which is more reliable, Public Time API or Webex?

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

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

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

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

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

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