“This phone number cannot be used for verification”

“This phone number cannot be used for verification” is a decision Google makes on its own servers, before it sends a single SMS. It has four separate causes — a flagged or disabled account, an undisclosed per-number account cap, the line type, or the number's format — and each takes a different fix. One of them has no fix at all. The standard advice — “use a different number” — is wrong for three of the four, so the first job is working out which one you're in.

What the message means, and the message people confuse it with

Google shows two strings and treats them as two different problems. One is “This phone number cannot be used for verification.” The other is “This phone number has been used too many times for verification.” Google's help page names both, and for both it gives a single instruction: use a different number (read 2026-08-12). That instruction fits one of them. For the other it misleads.

“Too many times” is a counting problem — you, or whoever held the number before you, hit a limit on how many accounts one number may create. “Cannot be used” is broader. It is frequently thrown at people whose account is the thing Google is blocking, where no number will ever work. The help page names neither VoIP nor virtual lines anywhere on it (verified by direct fetch, 2026-08-12), and it never says what the limit is. Those two silences are most of this article.

First: which failure are you in? A four-way triage

The listicles skip this step and jump to fixes, which is why the fixes miss. Match your symptom to a cause before you touch anything. The table sorts by what you can actually observe — whether the error follows every number, whether you can still reach other Google products, whether only rented numbers get refused.

Cause 1: the account, not the number

When the error follows you across every number — including the SIM in your pocket — the number is not the problem. Your account is. Google throws this same string at accounts it has flagged or disabled, and a fresh number cannot open a door locked from the account side. On the reports below, and against everything the ranking pages say, this is the most common version of the error in 2026 — and it is the one the top 10 does not mention.

It is not new. A 2016 engineering write-up on Medium (Around25) traced it to the end: the author's Google account had been disabled, and “this phone number cannot be used for verification” was the wall Google put in front of that fact — resolved five days later through an appeal, the number never having been the issue (22 April 2016). Ten years on, the same story fills r/GMail: threads like “Disabled Account Recovered — Can't Verify to Login” and “Disabled Google account + phone verification blocked,” where the account comes back and the phone error still blocks sign-in across browsers and connections (read via the arctic-shift archive, 2026-08-10). These are individual reports, not a measurement. Two of them, ten years apart, telling one story — that is the point.

So the first check costs nothing and needs no new number. Can you still open another Google product — Gmail on the web, YouTube, Drive — on the same account? If every Google surface refuses you, the account is the block, and account recovery is the path, not verification. A rented number pointed at the signup box is pointed at the wrong wall.

Cause 2: the quota nobody will name

Google limits how many accounts one phone number can create. It says so on its help page, then stops — it will not tell you the number. That is deliberate. Asked the size directly on Google's own AdWords API forum, Josh Radcliff of the AdWords API Team confirmed the per-number limit exists and declined to publish it, offering no way to reset it or age it out (15 June 2015). Eleven years later that thread is still the best public answer to the question, which tells you how much Google wants it discussed.

So the honest version is short: we don't know the cap, and Google won't say. What we can tell you is its shape. It counts per number, not per account — every account ever verified on that line adds up, including whoever held the number before you if it was recycled. Numbers get recycled between holders, and a number's history travels with it; our own terms spell out that a rented number may still carry messages meant for a prior holder. If you are seeing “used too many times,” you have hit the cap, and the only lever is a number that hasn't. A different number already near its own cap fails the same way.

Cause 3: line type, checked before anything is sent

Before Google generates a code it looks up what kind of line your number is. Mobile lines pass. Virtual and VoIP ranges get refused at that step often enough that a number which works fine for calls can still be rejected here. How that lookup works, and why VoIP gets screened, is the whole subject of why SMS codes don't arrive — so this page won't repeat it. One consequence does belong here.

The detection that stops disposable email addresses has a phone equivalent: a maintained blocklist, applied at signup. Castle publishes one — a public file of disposable and virtual ranges in E.164 form that rebuilds every day (read 2026-08-12). The check takes thirty seconds: open the file, search for your number, see whether today's list carries it. Don't read a single entry as a verdict — the file regenerates daily, so it is a snapshot, not a sentence — but a number sitting on a public disposable list is a number many services will treat the way Google just did.

Cause 4: formatting — the ten-second one

Rule out the cheap cause before the hard ones. The number has to reach Google in the shape it expects — country code, no leading zero on the national part, no stray spaces or dashes a field might mishandle. That is E.164. A UK mobile typed as 07700 900123 instead of +44 7700 900123 can bounce for a reason that has nothing to do with your account or your line.

Three checks take about ten seconds. Confirm you have signal and can receive an ordinary text. Re-type the number, country code included, instead of trusting autofill. And if Google offers to call rather than text, take it — a voice code routes differently, and sometimes lands where the SMS didn't. If none of that moves it, the cause is one of the three above, not the format.