"This Phone Number Cannot Be Used for Verification"
You typed in your real phone number, the one in your pocket, and the site refused it: "This phone number cannot be used for verification." No code was sent, nothing to troubleshoot on your handset, just a flat no.
The wording is unhelpful on purpose. Platforms deliberately keep these messages vague so that people probing their fraud systems learn as little as possible. But the error is not random, and it is almost never about you personally. It is a statement about the number — its type, its history, or how many times it has been through that platform's verification system before. This guide decodes what each major platform means when it shows you that sentence, and what actually clears it.
What "this phone number cannot be used for verification" actually means
Google, which shows this exact string more than anyone, documents two separate errors that people routinely confuse:
- "This phone number cannot be used for verification." Google's explanation: "To protect you from abuse, we limit the number of accounts each phone number can create." This is about account creation.
- "This phone number has been used too many times for verification." Google's explanation: "To protect you from abuse, we limit the number of times a phone number can be used for verification." This is about verification events, including sign-ins and recoveries.
Google does not publish the actual thresholds, and it would be worthless if it did — they are adaptive and vary by country, by carrier, and by how the number has behaved. Google's own advice when you hit the wall is blunt: use "a number from a friend, family member, or a different carrier."
That last phrase matters more than it looks. A different carrier. Google is telling you the block is attached to the number's carrier identity, not to your device, your browser, or your IP address. Clearing cookies will not help. Neither will a VPN.
The same error, platform by platform
Every large platform runs the same basic check with different wording. Knowing which sentence you are looking at tells you which of the four causes below you are dealing with.
| Platform | What you see | What it usually means |
|---|---|---|
| Google / Gmail | "This phone number cannot be used for verification" | Account-creation cap reached, or the number failed the carrier-type check |
| Google / Gmail | "This phone number has been used too many times for verification" | Verification-event cap; usually clears with time |
| Microsoft / Outlook / Azure | "Sorry, we do not accept Voice over IP (VOIP) numbers. Try again with a different number." | Explicit number-type rejection — the most honest error of the bunch |
| Discord | "This phone number is unable to be associated with this account" | The number is already attached to another Discord account |
| Discord | "Invalid phone number" | Formatting problem, or a landline/VoIP number, which Discord does not accept |
| Telegram | "This phone number is banned" | The number itself is flagged, often from a previous owner's activity |
| Registration fails or loops without a code | Number type unsupported, or a rate limit after repeated attempts |
Microsoft deserves credit here: it names the problem outright. Its support guidance is that verification requires a number able to receive SMS or a voice call from a US-based telephone number, and that standard mobile and landline numbers work while VoIP numbers do not. Everyone else makes you guess.
The four things that actually trigger it
1. The number is classified as VoIP
This is the single most common cause, and the most invisible, because the rejection happens in well under a second — before any SMS is ever attempted. The site queries a carrier lookup service, reads back the line type attached to your number, and refuses anything returned as VoIP. Google Voice, Skype, TextNow, most free "receive SMS online" numbers, and a good number of business phone systems all resolve this way.
The frustrating part is that a VoIP number is a perfectly functional phone number. It rings. It receives texts from your friends. It simply carries a different label in the industry databases every signup form consults. We break down exactly how that lookup works in how websites detect VoIP numbers, and what the classification means in plain terms in what is a non-VoIP number.
Tell-tale sign: the rejection is instant and identical every time, no matter how long you wait.
2. You have hit the platform's cap for that number
Every major platform limits how many accounts one number can vouch for. Google allows a small handful; WhatsApp, Telegram and Discord are effectively one account per number by design, because the number is the account identity.
If you are trying to keep a genuine work identity separate from a personal one — a support line for your business, a developer test account, a second Telegram tied to a company number — you have not done anything wrong, you have simply run into a design constraint. That case needs a second real number rather than a workaround. Deliberately cycling numbers to get past a cap the platform set is a different thing, and it tends to end with the account flagged anyway.
Tell-tale sign: the number works fine everywhere else, and worked on this platform before.
3. The number was recycled and arrived with baggage
US numbers get reused constantly. Under FCC rules, a permanently disconnected number must be reported to the Reassigned Numbers Database and aged for a minimum of 45 days before it can be handed to someone new. Forty-five days is the floor, not the norm, but it is short enough that a number issued to you this month may have been someone else's last quarter.
The database now covers more than 361 million geographic and toll-free numbers, with carriers reporting disconnections monthly — large and medium providers since April 2021, smaller ones since October 2021. That system exists so callers can avoid dialling strangers, but it does nothing about the mess left behind inside individual platforms. If the previous holder registered a Telegram account on your number and got it banned, Telegram still remembers the number, not the person. You inherit the ban.
Tell-tale sign: a brand-new number, from a legitimate carrier, that fails on exactly one platform.
4. Carrier and route reputation
Beyond the binary VoIP/not-VoIP split, platforms score the carrier itself. Numbers from small MVNOs, certain prepaid ranges, and carriers with a high historical volume of throwaway registrations get treated more suspiciously than numbers from the big four US networks. This is why two non-VoIP numbers can behave completely differently on the same signup form.
Tell-tale sign: inconsistent results — accepted on one site, refused on another, with no obvious pattern.
Work through it in this order
- Check the country code and format first. It sounds trivial and it is occasionally the whole problem. Enter the number in full international form and make sure the country dropdown matches. A US number entered with a leading 1 inside a field that already prepends +1 will fail as invalid.
- Try the voice-call option. Where a "Call me instead" link exists, take it. Voice and SMS sometimes travel different routes with different filters, and a number that cannot receive the text may still take the call. Microsoft explicitly suggests this and asks you to allow up to four minutes.
- Identify your number's line type. Run it through a carrier lookup before assuming anything. If it comes back as VoIP or "non-fixed VoIP", stop troubleshooting — no amount of retrying will change a classification.
- If it is a cap, wait rather than retry. Verification-event limits usually decay. Hammering the form resets the clock and can escalate a soft limit into a hard flag. Leave it 24 to 72 hours before the next attempt.
- Use the platform's alternative route. Google will often accept a recovery email, an existing signed-in device, or a security key in place of SMS. Telegram frequently sends the login code inside the app to a device you are already signed in on, rather than by text. Check for these before hunting for another number.
- If nothing clears it, the number is the problem. At that point you need a different number of a type the platform accepts — a real mobile-carrier line, not another internet number.
What does not work
A short list, because a lot of advice online is simply wrong:
- VPNs and cleared cookies. The check is on the number, not your connection.
- Free public "receive SMS online" numbers. These are shared, heavily reused, and already burned on every large platform. They are also public — anyone can read the codes sent to them, which makes them unsafe for anything you care about.
- Google Voice for Google, or for most other platforms. Google will not verify a Google account with a Google Voice number, and it fails widely elsewhere. The full picture is in does Google Voice work for SMS verification.
- Re-submitting the same number repeatedly. This is the most common mistake. Each failed attempt adds signal against the number.
When you legitimately need a different number
There are ordinary reasons to verify with something other than your personal SIM. You may be outside the US and need a US number for a service that only accepts one. You may not want your private mobile number sitting in a marketplace or dating app's database, given how routinely those get breached. You may be a developer needing a clean number for testing, or a business verifying a support line rather than an employee's personal phone.
For all of those, the requirement is the same: a number that carrier lookups classify as mobile rather than VoIP, and that has not been through the platform already. That is the entire specification. If you are comparing providers, we wrote an unsentimental rundown in best SMS verification services in 2026, and a broader list of rejection causes in why was my phone number rejected for verification.
FAQ
How long does "this phone number cannot be used for verification" last?
If it is a verification-event limit, typically hours to a few days, and it clears on its own. If it is an account-creation cap or a number-type rejection, it does not expire at all — the number will keep failing indefinitely. The test is whether the rejection is instant (type problem) or comes after the form appears to try (rate limit).
Can I fix it by getting a new SIM from the same carrier?
Usually yes for a type or history problem, since you get a different number. But you may land on a recycled number that carries its own history, so it is not guaranteed. If the block was a per-account cap on the platform, a new number solves it only where a second account is legitimate in the first place.
Does a landline work for verification?
It depends on the platform. Microsoft accepts landlines that can take a voice call. Discord and WhatsApp are built around mobile numbers and generally will not take one. If a "call me instead" option is offered, a landline has a reasonable chance; if only SMS is offered, it will not.
Why did the code go to someone else?
Almost always number recycling. If a platform still has an old registration attached to the number you now own, its records point at that stale account. This is the same 45-day reassignment problem described above, and it is fixed by contacting the platform's support rather than by retrying.
The short version
That error is the platform telling you something about your number's classification, history, or usage count — never about your identity. Find out which of the four it is before you do anything else. If the rejection is instant, it is the number's type and no retry will help. If it arrives after a pause, it is a limit and time is the fix. And if you keep resubmitting the same number hoping for a different answer, you are actively making it worse.