Live measurements, updated 2026-10-28
Latency, cost, and language coverage, with the methodology on each. If a figure moves, this page moves. Everything here is cite-able.
A translated phone call is a pipeline of five stages, each with its own budget. These are the actual numbers we measure, published so anyone writing about live call translation has a primary source to cite.
Each tile is a named, dated claim with the methodology beneath. Cite freely; the page URL is the primary source.
Average call-translation latency, European language pairs
420 ms
End-to-end latency, measured in 2026 across 1,247 translated calls between English, Spanish, Hungarian, French and German, inclusive of audio capture, speech-to-text, machine translation, text-to-speech, and SIP delivery.
ChromePing internal latency canary, Q3 2026. Methodology: five-stage pipeline measurement with sub-second granularity. See the latency glossary entry.
Text-to-speech first-audio latency
280 ms
Time from a finalised translated-text payload to the first audio frame reaching the recipient's phone. Measured with Telnyx's low-latency TTS as the production default; Cartesia voice-cloned path adds about 150 ms.
ChromePing internal measurement, 2026.
Cost of a 5-minute translated browser call to Spain
about $0.70
Based on ChromePing's October 2026 per-minute rate to Spanish landlines plus the live-translation surcharge. The rate index publishes the live number for every country.
ChromePing live rate index, October 2026.
Cost of a 5-minute translated browser call to Mexico
about $0.85
Mexican landline rate plus the live-translation surcharge. Mobile calls to Mexico run slightly higher; see the live rate index for the exact figure.
ChromePing live rate index, October 2026.
Cost of a 5-minute translated browser call to Japan
about $1.10
Japanese landline rate plus the live-translation surcharge. The rate includes keigo-register translation on the pipeline's default path.
ChromePing live rate index, October 2026.
Languages verified end-to-end live in production
4
English, Spanish, Japanese, and Hungarian are verified live end-to-end today. Other languages are in the pipeline but not yet marked production-ready. ChromePing deliberately does not publish an aspirational count.
ChromePing product brief, 2026.
Latency numbers come from a canary job that places a translated call once an hour on every supported language pair and records the five-stage breakdown: audio capture and encoding, transit to the server, speech-to-text finalisation, machine translation, and text-to-speech first-audio. The 420 ms headline is the median across European pairs; individual pairs vary by ±90 ms.
Cost numbers come from the live rate index at /rates, multiplied by the flat live-translation surcharge and the stated call duration. The per-country rate updates automatically; the surcharge is published once and rarely changes. Both figures are per-second billed, with the first minute billed in full.
Language coverage is the deliberate subset the product team has verified end-to-end in production, not an aspirational list. Translation accuracy varies by language pair even inside this set; the stats page is the headline, not the depth guarantee.
Each stat has its own anchor fragment (for example, /stats#latency-european-pairs) and a corresponding Claim JSON-LD node pointing to it. For a published article, cite the page URL plus the stat’s headline. For a podcast or a research paper, email press@chromeping.com and we’ll confirm the specific figure for your date of publication.
For deeper methodology on the five-stage pipeline, see how real-time call translation works. For the latency glossary entry, see /glossary/latency.
Dial mobiles and landlines in 25 countries from a browser tab and turn on live translation when the conversation crosses a language. The numbers above are what you can expect.
Monthly plans from $9.99. Rates vary by destination. Not for emergency calls.