Public Time API vs Remotive
Same instrument, two spec sheets — measured, not claimed.
Public Time API vs Remotive: common questions
Which is more reliable, Public Time API or Remotive?
Both are neck-and-neck — Public Time API and Remotive 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, Public Time API or Remotive?
Public Time API has the lower median latency in our checks — Public Time API responds in 242 ms versus Remotive at 612 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 Remotive need an API key?
Neither needs a paid key — Public Time API is callable with no signup, and Remotive is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call Public Time API and Remotive from the browser?
Only Remotive 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 Remotive free for commercial use?
Public Time API has unclear commercial terms, and Remotive 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.