"This phone number cannot be used for verification" means the platform looked up your number and rejected it before sending anything. The most common causes are a VoIP or virtual number, a number already attached to too many accounts on that platform, and a temporary block from repeated attempts or a low-reputation connection. Clearing cache, updating your phone or reinstalling the app fixes none of them, because the decision happens server-side on the number itself.
Read the exact wording first
The wording tells you whether the rejection is about the number or about the moment.
| Message | What it means | What actually fixes it |
|---|---|---|
| This phone number cannot be used for verification | The number failed carrier lookup (VoIP, virtual, or a range the platform blocks) or hit its lifetime account limit | A different non-VoIP carrier number. Waiting changes nothing |
| This phone number cannot be used at this time | Temporary throttle: too many codes requested to that number, or too many attempts from your IP or device | Wait at least a day, then retry once from a stable connection |
| Too many attempts / try again later | Rate limit on the request side, not the number | Stop retrying. Each retry extends the window |
| Code sent but never arrives | Number accepted, delivery failed (carrier filtering, forwarded VoIP leg, roaming) | Request a voice call instead, or use a number on the carrier's own network |
If you see the permanent wording, every step that involves your handset is wasted effort. Change the number.
Cause 1: the number is VoIP or virtual
Google, WhatsApp and many other consumer platforms check your number against carrier lookup data before sending a code. If the lookup returns a VoIP carrier, a hosted PBX, a messaging-app number, or a range known for bulk resale, the request is refused. Google Voice, Skype, TextNow, Phone.com and similar services typically land in that bucket, which is why the same number can work fine for banking SMS and still be rejected by Gmail.
Number portability makes this messier: a landline number ported to a VoIP provider keeps its original area code, so it looks local while the lookup returns VoIP. The mechanics of how those lookups work are covered in why VoIP numbers fail SMS verification and how platforms detect VoIP and virtual numbers.
Fix: use a non-VoIP carrier number. On VoidMob that means a one-time OTP (US numbers, from $0.95 on Google/Gmail), a multi-day US rental if you need to keep the number for 3 to 30 days, or a dedicated monthly non-VoIP line if the account will need re-verification, password resets and 2FA later. Which of the three fits depends on the account's lifespan: dedicated number vs OTP walks through the trade-off in full.
One-time OTP window
A one-time OTP number stays active for 15 minutes. Reusing the same number inside that window is free, so a failed first send is not a wasted purchase. If no code arrives before the window closes, the rental auto-cancels and refunds in full.
Cause 2: the number is used up
Most platforms cap how many accounts one number can verify, and the cap is usually invisible until you cross it. Google does not publish its limit, but once a number has verified enough accounts it returns the permanent rejection even though it is a real carrier line on a real SIM in your hand.
Two consequences worth planning around:
- Recycled numbers arrive pre-spent. Carrier numbers get reassigned, and the previous owner's account history travels with the number.
- Do not count on the budget resetting when you delete accounts. In practice, removing a Gmail account does not reliably release the number.
Fix: a number that has not verified that platform before. If you manage several legitimately owned accounts, assign one number per account rather than cycling one number through all of them. Multi-accounting safely: SMS numbers that don't burn out covers the assignment pattern.
Cause 3: your connection is being scored, not just your number
Platforms decide whether to send a code at all based on the whole request, not only the digits. A signup from a datacenter IP, a public VPN endpoint, or an address with a recent abuse history frequently gets the "at this time" variant, or a code that never arrives, even with a clean carrier number. Google's QR-code and device-verification prompts on new accounts appear to be driven by similar connection signals: why Google requires QR codes for new accounts explains what it is reading off the connection.
Check what the platform sees from your current exit before you spend another number:
See how your connection looks to the verification server
If the result comes back as datacenter or VPN, move the flow onto a residential or mobile exit and try once. Real 4G/5G exits behind carrier NAT look like the phone the platform expects a phone number to belong to, which is why verification and recovery flows for accounts you own run better through mobile proxies than through datacenter ranges. Location matters too: a US number verified from a connection three continents away is a mismatch the scoring model notices, so match the exit country to the number country and keep your browser timezone consistent with it.
The configuration detail that breaks otherwise-clean setups
Rotating the IP mid-verification is a common self-inflicted failure. The request for the code, the submission of the code and the first login afterwards should all arrive from the same address. On a rotating pool with per-request rotation, the code submission lands on a different device than the request, and the platform reads the mismatch as a broken session: some fail silently, some serve the "cannot be used at this time" message.
Pin the session for the whole flow. On VoidMob's flex gateway that means adding a session parameter to the username, for example <username>_c_US_s_signup1_ttl_30m, which holds one US device for 30 minutes. Keep the same session ID from the moment you request the code until the account is verified and logged in once, then release it. A sticky session is the mechanism; per-request rotation is what you want for scraping, not for verification.
Second detail: request the code once. Every extra tap during a throttle extends the cooldown, and repeated requests in a short window can turn a temporary block into a hard rejection for that number on that platform.
Order of operations
- Read the wording. Permanent means change the number, temporary means stop and wait.
- Confirm the number is non-VoIP. If it came from a calling app or a virtual number service, it is the cause.
- Confirm the number is unused on that platform.
- Check your exit IP type and country, and fix a mismatch before retrying.
- Pin the session, request the code once, submit it from the same IP.
- If the number is accepted but no code arrives, switch to the voice-call option where the platform offers it.
For platform-specific quirks, Google SMS verification and WhatsApp verification document the number types each accepts.
1How do I fix Google's "this phone number cannot be used for verification"?
Use a different non-VoIP carrier number and request the code once from a residential or mobile IP that matches the number's country. If the message includes "at this time", it is a throttle instead: wait at least a day and retry a single time. Clearing Google Play Services cache or updating the OS does not affect a server-side number rejection.
2Why can't I use my own phone number for verification?
Either it is not on a mobile carrier network (ported to VoIP, a calling-app number, or a landline), or it has already verified the maximum number of accounts that platform allows over the number's lifetime, including accounts created by a previous owner of a recycled number.
3What does "cannot verify phone number, this phone number cannot be used at this time" mean?
It is a temporary block. The platform counted too many code requests to that number, or too many verification attempts from your IP address or device, and paused the flow. The number itself is usually fine. Retrying immediately resets the cooldown clock, so stop for a day or more.
4Can I skip phone verification entirely?
Only where the platform offers an alternative itself: some make the number optional at signup, and some accept an email address or an authenticator app for two-factor setup instead. Where the number is mandatory, use a non-VoIP carrier number the platform accepts.
5Will a VPN cause the error?
It can. Public VPN and datacenter ranges carry heavy abuse history, so verification requests from them are frequently throttled or silently dropped. Check your exit type first, then run the flow from a mobile or residential IP in the number's country.
Get a number the platform accepts
Non-VoIP carrier numbers for one-time codes, multi-day rentals, or a dedicated monthly line, plus mobile exits for the signup flow.