VoIP vs non-VoIP numbers: why nobody can promise you a non-VoIP one

A non-VoIP number is a phone number carried on a mobile network — a SIM on a real carrier's range — rather than on an internet calling service like Google Voice. No provider can promise you one. The label is not stamped on the number; it is the answer a line-type lookup returns, and that answer can be stale, wrong, or come back “unknown.”

That single fact runs against most of what the category sells. Here is what the two types are, why the boundary between them is softer than a product page admits, and the one figure we counted that no reseller can wave off.

What separates a VoIP number from a non-VoIP one

Start with the definitions, because the vendors blur them on purpose. spenza.com — published 17 July 2026, read 2026-08-12 — draws the line cleanly: a VoIP number “sends and receives voice calls and text messages over an internet connection rather than a traditional cellular or landline telephone network,” while a non-VoIP number is “issued directly by a licensed mobile carrier … associated with a physical SIM card or eSIM.” Google Voice and a thousand app numbers are the first kind. The SIM in your pocket is the second. Strict platforms — the ones that gate signup on a phone number — try to tell the two apart and refuse the VoIP kind.

How that refusal actually happens — a line-type lookup at onboarding, a range sitting on a blocklist, a code dropped with no error on your screen — is not this page's job. Why SMS codes don't arrive owns that mechanism in full, and the wider family the term belongs to sits in what a virtual phone number is. What matters here is narrower, and it is the question the category depends on you not asking: who can actually certify that a given number is non-VoIP?

Line type is a lookup result, not a fact about the number

Ask what “non-VoIP” is at the moment a service checks it, and the answer is deflating. It is a database lookup. The service, or a vendor it pays, sends your number to a line-type API and reads back a classification. spenza names four of those vendors — Twilio Lookup, Telesign, IPQualityScore and Ekata (read 2026-08-12). Twilio's Line Type Intelligence hands back values such as “mobile,” “landline,” “fixedVoip” and “nonFixedVoip” (read 2026-08-12). So a number is “non-VoIP” only in the sense that some lookup, on some day, said so. Three things spoil that answer, and no reseller can fix any of them.

It is often a reseller's shared pool

spenza states the load-bearing thing outright, and it has earned the credit: “Many services that advertise ‘non-VoIP numbers’ are actually reselling virtual numbers drawn from shared pools” (read 2026-08-12). Its Honest Caveat goes further — a non-VoIP number “significantly improves your chances of passing verification. It does not guarantee it. Acceptance still depends on the individual number's history, the carrier it comes from, the country of origin, and each platform's specific risk policy.” Read that twice. The strongest page on this search already tells you the promise is soft. Where spenza asserts, we later counted — and that gap is the whole reason this page exists.

A ported number carries a stale row

Numbers move. A line can change carriers years after it is issued, and can even cross between types — a landline ported onto a mobile account, a mobile number handed to a VoIP app. Keeping a lookup current means consulting portability records, and that data is gated: Twilio's line-type documentation tells developers to request access to Canadian Number Portability Administration Center (NPAC) data to resolve it (read 2026-08-12). A cheaper check skips that dip and reads the number's original range instead. So a real mobile line can read as VoIP because its old prefix block says so, and a VoIP number can pass as mobile for the same reason. Even spenza's page, the fullest on this search, stops at the definition and its acceptance caveat and never reaches how a label ages. The classification you are sold is only as fresh as the database that produced it.

The lookup answers “unknown”

Sometimes the honest output is no output. Twilio's Line Type Intelligence carries a value it calls “unknown,” defined in its own documentation as “a valid phone number, but the line type is unknown” (read 2026-08-12) — and when carrier data is missing, the carrier fields come back null. A service that reads “unknown” has to choose: trust the number, or refuse it. Different services choose differently. That is why one number sails through a signup and the very same number is rejected at the next one. No reseller controls that coin toss.

We counted what the supplier catalogue actually holds

Here is the part spenza cannot give you, because it needs a supplier's own inventory rather than a public page. We counted, on 2026-07-27, the operator labels in the supplier catalogue we build against: 161,254 of 165,122 rows — 97.7% — were one opaque “virtual…” pool, against roughly twenty named operators in the whole catalogue. That is a count of what the catalogue held on that date. It is not a success rate, and it says nothing about whether a code arrives.

What it says is structural. When the real operator behind a number is never named upstream, a reseller passing that number along cannot substantiate a per-number “non-VoIP” label — even on the numbers where the label happens to be true. One example from the same count made the point sharply: UK WhatsApp inventory in that catalogue was two virtual pools, “virtual34” and “virtual66,” while every named UK carrier in it sat empty. spenza asserts that resellers cannot certify these numbers. We opened the drawer and counted the unnamed ones.

Why a “non-VoIP” promise can't be kept

Line the reasons up and the marketing claim thins into a probability. The label is a lookup. The lookup can be stale, or blank. The pool beneath it is mostly unnamed. And even a correct “non-VoIP” reading only holds until the number's history or a carrier filter sinks it anyway. spenza's own caveat lands in the same place from the outside — better odds, not a promise. A provider that stamps every number “non-VoIP” with full confidence is selling you the confidence of a database it does not run. The route-level view of the same decay — how a supply pool goes stale as it ages — is in how SMS verification routes fail.