Cisco Spark vs Public Time API

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

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

Cisco Spark vs Public Time API: common questions

Which is more reliable, Cisco Spark or Public Time API?

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

Public Time API has the lower median latency in our checks — Cisco Spark responds in 1608 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 Cisco Spark and Public Time API need an API key?

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

Can I call Cisco Spark and Public Time API from the browser?

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

Cisco Spark 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.