Public Time API vs Vonage (Nexmo) API
Same instrument, two spec sheets — measured, not claimed.
Public Time API vs Vonage (Nexmo) API: common questions
Which is more reliable, Public Time API or Vonage (Nexmo) API?
Both are neck-and-neck — Public Time API and Vonage (Nexmo) 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, Public Time API or Vonage (Nexmo) API?
Public Time API has the lower median latency in our checks — Public Time API responds in 242 ms versus Vonage (Nexmo) API at 507 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 Vonage (Nexmo) API need an API key?
Public Time API needs no key, while Vonage (Nexmo) API 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 Vonage (Nexmo) API from the browser?
Neither sends browser-friendly CORS headers reliably, so call Public Time API and Vonage (Nexmo) API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.
Are Public Time API and Vonage (Nexmo) API free for commercial use?
Public Time API has unclear commercial terms, and Vonage (Nexmo) 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.