“This phone number cannot be used for verification”
Google returns this before it sends anything. It can mean four things — a flagged account, an undisclosed account quota, the line type, or the format.
Pre-launch — you can read everything, but ordering isn't open yet. Where we are
On WhatsApp, “this number is already registered” almost always means someone reached the number before you did. Rented numbers are recycled, and a previous holder verified WhatsApp on yours. A fresh number usually clears it — though a couple of platforms make the binding permanent. This walks through which is which.
Three different failures wear near-identical words, and each routes to a different fix. Read the string the app actually shows before you spend anything.
One case looks like a taken slot and isn't. On Telegram, if you're signed in on another device the login code is delivered inside the app rather than by SMS — the FAQ says it may send the code “via Telegram instead of SMS” (read 2026-08-12). So a number that seems unreachable may simply have sent its code somewhere you didn't check. Look in the app first; if codes still stall, Telegram code not arriving covers the rest.
The number you rent is not new. It moved through the pool before it reached you and arrived carrying whatever its last holder did with it, a live WhatsApp registration included. How SMS verification routes fail covers the recycling in full, so this page won't repeat it — the short version is that the slot was claimed once and never released.
We put this in writing rather than bury it. Our terms state that a rented number can still carry registrations and messages meant for a prior holder — the same fact this page is about, disclosed before you order. If it is specifically WhatsApp you're verifying, verifying WhatsApp without your own number covers screening and re-verification in one place.
The rule that trips you is not a WhatsApp rule. Almost every consumer platform binds one account to one phone number, so a recycled number arrives pre-attached wherever its last holder used it. The wording differs. So does the escape route.
| Platform | The rule, quoted | Does a fresh number clear it? |
|---|---|---|
| One account per number; a taken slot returns “already registered” | Usually — re-roll to a fresh number | |
| Telegram | Mobile only — “we currently don't support landline numbers”; signed in elsewhere, the code arrives in-app, not by SMS | Usually — but check the in-app code first |
| Discord | “A phone can only be registered with one Discord account at a time” | Yes — but removing one starts a waiting period |
| “used too many times for verification” — a per-number cap | A cap, not a slot; a different number resets it | |
| Apple ID | Second-hand report: a number tied to one Apple ID “cant be linked to another, even after delinking” | Often not — a fresh number may be the only path |
Every quote in that table is from the platform's own pages, read 2026-08-12: Telegram's FAQ, Google's verification help, and Discord's Help Center, where the article “How to Fix Phone Errors on Discord” carries a net helpfulness score of −29,542 across 137,878 votes — a rough public measure of how routinely the phone step goes wrong. The Apple row is the odd one out: it is not an Apple document, and the next section explains why that matters.
The reason the rule exists is dull and consistent. One account per number is how platforms slow bulk signups and ban evasion, and the binding is built to be sticky — the whole point is that you can't cheaply shed it. That is why spinning up a second account rarely helps while a different number usually does: you are not fighting a bug, you are meeting a rule working as intended.
A re-roll assumes the block lives on the number, so swapping numbers walks past it. Two platforms break that assumption.
On Apple ID, the binding may outlive the number. A user relaying Apple Support on the Apple discussions forum (read 2026-08-12) was told that “once a number has been registered on one Apple ID, it cant be linked to another, even after delinking from the previous one.” Treat that as one support agent's account, not published Apple policy — but the thread's community moderator was blunt about the remedy: request a new number from your carrier. If a recycled rental is stuck to a stranger's Apple ID, a fresh rental is the only lever you have.
Discord adds a timer. Its Help Center states that after a number is removed, “there is a waiting period before the number can be used on an account again” (read 2026-08-12) — so if the taken slot is one you control, freeing it is not instant. And if you don't know the email on the account holding the number, Discord says its “Support team will not be able to provide this information, or remove the number.” A fresh number sidesteps both. If Discord specifically is failing you, Discord verification failing walks the full path.
You can't see a number's account history, but you can check whether the wider ecosystem already flags it as a throwaway. Castle publishes an open disposable-phone-numbers list (read 2026-08-12) — roughly a thousand numbers in E.164 form, regenerated daily. Paste the number you were handed into it. A hit doesn't prove your number is spent, and one list is never a verdict — but a number a public blocklist already carries is one the big platforms have had every reason to flag too. If it shows up, switch routes rather than re-rolling inside the same range.
The honest limit is worth stating plainly: we can't see a number's history before it reaches you. We counted the supplier catalogue we buy from on 2026-07-27 — 161,254 of 165,122 operator rows, or 97.7%, are an opaque “virtual” pool with no named operator behind them. That opacity cuts both ways, and this is the side that stings: no reseller, us included, can promise a specific number is unused before you rent it. Whether a given route tends to hand out fresh numbers or worn ones is a measurement we don't have yet, and we won't invent one:
We don't have data for this route yet
That sentence sits on routes we haven't measured, popular ones included. What we do commit to is written down: how recycling and prior-holder messages are handled is on the trust page and in the terms. If you want a fresh WhatsApp number to re-roll, every price and route state is readable without an account on pricing.
Neither, usually. It means the number was verified on the app before you rented it — a recycled number that arrived with its slot taken. Nobody is targeting you, and the app has not banned the number. Re-roll to a fresh one and try again.
Once or twice is reasonable. Past that you're paying to sample the same worn pool. If several numbers on one route come back “already registered,” switch routes rather than numbers — every price is public, so comparing costs nothing. On Telegram specifically, confirm first that you aren't simply being handed the code inside the app instead of by SMS.
On the platforms that impose a wait, sometimes. Discord's Help Center describes a waiting period after a number is removed before it can go on another account (read 2026-08-12). That only helps when the slot is one you control and can free, though — a recycled rental taken by a stranger is not yours to remove, and Apple's reported binding doesn't lift on any timer. When the slot isn't yours, time won't return it. A fresh number will.
Probably not, going by Apple's own support channel. A user relaying Apple Support (read 2026-08-12) was told a number stays bound to its first Apple ID even after delinking, and the community moderator's fix was to get a different number. If the number came from a rental pool, that means a fresh rental — the old binding isn't yours to release.
Every route shows its price and its data state up front — and where we have nothing yet, it says so.
Every route below is one click away. Open a country to see its services, or jump straight to a service hub.