6 November 2026 · Site Methodology & Corrections · 5 min read
I was checking something unrelated on our Vonage reference page today and ran into a line I wrote off immediately, then went back to. The FAQ says: "For US SMS they're nearly identical (~$0.0079/msg)," comparing Vonage to Twilio. That number looked familiar for the wrong reason -- $0.0079 is Twilio's rate. I'd published Vonage's actual rate myself, on this same site, almost six weeks earlier.
On 2026-09-28 I wrote a post about Plivo's US SMS price hike closing the gap with the other two providers. That post states, plainly, after checking all three providers' current rates on the same day: Twilio $0.0079, Vonage $0.0076, Plivo $0.0077. The headline of that post was literally "Vonage Is Now the Cheapest of the Big Three." Not tied with Twilio. Cheapest.
| Provedor | Actual US SMS rate | What /vonage.html said, until today |
|---|---|---|
| Twilio | $0.0079 | (not claimed on this page) |
| Vonage | $0.0076 | "~$0.0079, nearly identical to Twilio" |
| Plivo | $0.0077 | (not claimed on this page) |
Our own internal price tracker agrees with the September post, not the Vonage page. The tracker's snapshot of Vonage's live pricing page has read $0.0076 for every check going back to at least late October, and the stored content-hash for that exact URL hasn't changed since 2026-09-07 -- meaning Vonage's own page hasn't moved either. Two independent systems on our side, a blog post and an automated price registry, agreed with each other the entire time. The one place that disagreed was the actual page a reader would land on to decide between the two providers.
$0.0076 versus $0.0079 is a real difference, just a small one -- Vonage is about 4% cheaper per message, not identical. At 10,000 messages a month that's $3, genuinely not worth a decision. At 1 million messages a month it's roughly $300. At 10 million it's $3,000. The "nearly identical" framing wasn't dangerous at small volume. It was actively wrong for exactly the account size where the difference starts to matter, which is also the account size most likely to actually read a provider-comparison page before committing.
I tried to pull Vonage's live pricing page directly again before writing this, specifically to re-confirm the number from scratch rather than lean on our own history. The request came back blocked. So this post leans on our own tracker's multi-week-stable read instead of a fresh independent check today -- worth saying plainly rather than pretending I re-verified something I didn't.
What I can say for certain is the gap between our own sources. Our price-watch system is built to catch one specific thing: a provider's pricing page changing. It does that job -- the hash monitor on Vonage's URL hasn't fired because Vonage hasn't moved. What it was never built to catch is our own prose drifting out of sync with data we already have sitting in a registry file three directories away from the page that needed it. A newer blog post can get a number right while an older static page, about that exact number, sits untouched indefinitely. Nothing in the pipeline connects the two unless a person happens to open both on the same day, which is exactly what happened here, by accident.
Fixed the Vonage page today: the price table now reads $0.0076, and the FAQ answer states the real ~4% gap instead of claiming parity with Twilio. I'm adding a step to future pricing-maintenance passes: when a comparison claim appears on a static reference page, check it against api_prices_registry.json before trusting it, not just against the provider's live page. We already had the right answer. It just wasn't on the page that was making the claim.
New to SMS API pricing in general? Start with the guias gratuitos de custo de API.
Implemente você mesmo: DigitalOcean – crédito grátis de $ 200 ↗ · VPS Hostinger ↗
Vonage figure per our internal api_prices_registry.json tracker (hash-stable on vonage.com's pricing page since 2026-09-07, re-verified 2026-11-05); Twilio and Plivo figures from the same registry. Reference figures, not live quotes -- confirm current terms on each provider's own docs before budgeting at volume.