You hit “Send code,” the countdown starts, and then… nothing. No SMS, no error message, just a spinning button and a deadline. If you are searching for a fix because the SMS verification code never arrived, you are in the right place.
Verification codes fail for a surprisingly small number of reasons, but those reasons live in three very different places: the platform sending the message, the carrier or SMS aggregator delivering it, and the number or device receiving it. Most troubleshooting guides only cover the last one, which is why people keep retrying the same broken step.
This guide works through all three layers, in the order that actually solves problems fastest. Fifteen causes, fifteen fixes, plus a way to test whether a number can receive SMS before you commit to it.
Start here: the 60-second diagnostic
Before reading all fifteen causes, run this quick triage. It routes you to the right section.
| Symptom | Most likely cause | Jump to |
| No SMS at all, ever, on this number | The number cannot receive SMS (VoIP, fixed-line, or blocked range) | Causes 1, 4, 5 |
| Worked before on this number, stopped now | Resend throttle or platform risk control | Causes 6, 7 |
| Code arrives 10–30 minutes late | Carrier queue or aggregator routing | Cause 10 |
| Other people’s codes arrive, one service’s never does | Sender-side filtering of that service’s short code | Causes 11, 12 |
| “Too many attempts” error | Rate limiting, not delivery failure | Cause 6 |
| Code arrives but is rejected as invalid | Expired code or a stale message thread | Causes 3, 6 |
Layer 1: Problems with the number itself
This is where the majority of “code never arrived” cases actually sit, especially for anyone using a rented or online number.
1. The number is a range that cannot receive SMS at all
Not every phone number is SMS-capable. Numbers are classified by type — mobile, fixed-line, VoIP — and many fixed-line and VoIP ranges simply have no SMS termination route. When a platform sends to one of those, the message is dropped upstream and you never see an error.
Fix: Check the number type before you rent or buy, not after. If a service offers both virtual and real mobile numbers, match the type to what the platform requires. A real mobile number has the widest compatibility; a virtual number is cheaper and easier to spin up but can be rejected by stricter platforms. (We compare the two in detail in virtual vs. real phone numbers for SMS verification.)
2. Wrong country code or a mangled format
Platforms accept numbers in E.164 format — a+, country code, then the subscriber number with no spaces, dashes, or leading zero. Enter 0044 7911 123456 and you may get a silent failure instead of a validation error.
Fix: Strip the trunk prefix. UK 07911 123456 becomes +447911123456. German 0151… becomes +49151…. If the field already shows a country selector, do not retype the country code inside the number box — that produces +1 +1 415… and the message goes nowhere.
3. The number is already tied to another account
Most platforms allow one account per phone number, and some keep the link after the account is deleted or deactivated. If you are re-verifying a number, the code may be suppressed because the platform considers the number already used.
Fix: Log in to the old account and change the number there first, or request a fresh number. Reusing a rented number across multiple services is also a common cause of silent failures — see our guide on choosing a number for account verification.
4. The platform blocks the number range
Fraud teams maintain blocklists of number ranges that historically generated abuse. If your number falls inside one, the platform may accept it in the form and then quietly decline to send — a deliberate anti-enumeration tactic, because a visible error would tell bad actors which ranges to avoid.
Fix: Try a different number in the same country before assuming the platform is broken. If three numbers from one provider all fail and one from another provider works, the block is on the range.
5. The rental expired or the number was reassigned
Temporary numbers have a lifetime. Once the rental window closes, the number returns to the pool and may be issued to someone else. Any message sent after that goes to the new holder — or nowhere.
Fix: Check the rental end date in your dashboard before starting a verification you cannot afford to repeat. If you will need the account long-term, rent for the full period you intend to keep the account, because re-verification on login is common.
Layer 2: Problems on the sending platform
6. You hit the resend throttle
Every platform limits how often it will send a code to one number, usually somewhere between 30 seconds and several hours depending on the service and how many attempts you have made. The UI often does not say “you are rate limited” — it just stops sending.
Fix: Wait the full cooldown before retrying. Hammering the resend button resets or extends the timer on many platforms. If you have burned through several attempts, waiting an hour is faster than continuing to click.
7. Risk control flagged the signup
Device fingerprinting, VPN detection, a datacenter IP, or an unusual country mismatch between IP and number can push an account into a “verify later” queue where codes are delayed or suppressed.
Fix: Turn off the VPN for the verification step, use a residential connection, and keep the number’s country consistent with your apparent location. Then retry once — not five times.
This is also why free public SMS inboxes fail so often: the same number has been used for hundreds of signups and is already flagged everywhere. We break that down in WhatsNumber vs. free SMS websites.
8. Region mismatch between number and IP
A US number verified from an Indonesian IP on a service that geo-restricts registration is a classic silent failure. The code may be sent and then dropped by the platform’s own fraud layer.
Fix: Match number country to your connection country. If that is not possible, expect some platforms to refuse regardless of number quality.
9. The platform switched to a call or an in-app code
Not every “SMS code” is an SMS. WhatsApp falls back to a voice call, Telegram sends the code inside the app if you are already logged in elsewhere, and some services push the code to an authenticator app instead. You may be waiting for a message that was never going to be an SMS.
Fix: Look for a “Call me” or “Verify by call” option. On platforms with an existing session, check in-app notifications and linked devices.
10. Nothing was actually sent
Aggregator queues back up. Twilio-style providers, regional SMSCs, and carrier routes can delay messages by minutes to hours, and occasional outages on a single route are normal.
Fix: Wait ten minutes before assuming failure, then try a second number. If two different numbers from two different providers both fail on the same service, the problem is upstream, and no amount of retrying on your end will help.
Layer 3: Problems on your device or inbox
11. Spam filters ate the message
Android’s Messages app filters unknown senders into “Spam & blocked,” and many carriers run their own short-code filters. Verification messages arrive from 5–6 digit short codes, which is exactly the pattern filters are trained to suppress.
Fix: Open Messages → Spam & blocked and check. On iOS, check Messages → Filters → Unknown Senders. Whitelist the short code if you can see it.
12. RCS or iMessage intercepted the thread
If a service previously messaged you over RCS (Android) or iMessage, the thread may continue on that channel and the SMS never lands in the SMS inbox. WiFi Calling can also route SMS through a different path with its own failure modes.
Fix: Toggle RCS or WiFi Calling off temporarily and request a new code. Then re-enable.
13. Focus mode, DND, or a silent unknown-sender setting
These rarely block delivery, but they do hide the message — and in a two-minute countdown, “hidden” and “not delivered” look identical.
Fix: Turn off Focus/DND for the verification window and search the inbox by sender rather than scrolling.
14. Third-party spam and caller-ID apps
Apps that screen unknown numbers can quarantine SMS too. Installing one to avoid spam is a common reason verification codes stop arriving.
Fix: Disable the blocker for ten minutes.
15. Dual-SIM sent the request from the wrong line
On dual-SIM phones, the SMS thread may live on the SIM you are not looking at, or the app may have registered the wrong line’s number.
Fix: Check the SMS inbox of both SIMs, and confirm which number the app actually stored in settings.
How to test a number before you rely on it
You cannot fix a delivery failure you cannot see, so test first:
- Send yourself a known message. Use a service that sends an immediate confirmation SMS on signup, or ask a colleague to text the number.
- Check the message timestamp, not just arrival. A 20-minute delay tells you the route is slow, which matters if the platform’s code expires in 5 minutes.
- Test on the target platform with a throwaway account before using the number for anything you care about.
- Test twice, spaced an hour apart. A number that works once and fails on the second send is usually rate-limited or already flagged.
- Record which number worked for which platform. Reuse only the numbers that have a track record.
If you are verifying several services, run these tests on a dedicated number rather than your primary one. Private rental numbers give you your own inbox and a number nobody else is hammering — the reason we built WhatsNumber around rental access instead of a public inbox.
When to switch to a real mobile number
Virtual numbers are the right default for one-off verifications and privacy-sensitive signups. They are the wrong choice when the platform is strict, when you need the account long-term, or when the number must survive re-verification months later.
| Situation | Virtual number | Real mobile number |
| One-off signup on a mainstream app | ✅ | Optional |
| Platform known to block VoIP ranges | ❌ | ✅ |
| Account you must recover later | Risky | ✅ |
| Testing dozens of signups | ✅ | ❌ too expensive |
| Number needed for 12+ months | ✅ if renewed | ✅ |
| Regulated services (banking, payments) | Usually rejected | ✅ |
A realistic split: use virtual numbers for the 80% of services that accept them, and keep one real mobile number as the fallback for the ones that don’t.
FAQ
Why am I not receiving SMS verification codes from any service?
If every service fails, the problem is the number or the device, not the platforms. Check that the number is SMS-capable, that the inbox is not filtered, and that the SIM or rental is still active. A number that receives nothing at all usually has no SMS termination route.
How long should I wait before requesting another code?
At least 60 seconds, and ideally 10–15 minutes if the first attempt failed. Many platforms extend the cooldown with each request, so rapid retries can lock you out for hours.
Why does the code arrive but get rejected as invalid?
Codes expire — typically within 5–10 minutes — and older messages in the same thread can be mistaken for the new one. Always use the most recent message and check the timestamp.
Do virtual numbers work for SMS verification?
Often, yes, but not universally. Virtual numbers are more likely to be blocked by strict platforms, and VoIP ranges are sometimes rejected outright. Real mobile numbers have the highest acceptance rate.
Can a VPN stop verification codes from arriving?
Yes. A VPN can create a country mismatch that triggers fraud checks, and some platforms suppress codes rather than showing an error. Disable it during verification.
Is there a way to avoid this next time?
Use a number you control with a private inbox, verify the number type before renting, and avoid reusing numbers across many services. A number with no history of abuse gets codes delivered far more reliably.
The short version
Codes usually go missing in one of three places: a number that cannot receive SMS, a platform that decided not to send, or a device that hid the message. Work the layers in order — number type, then resend limits and risk flags, then device filters — and you will solve most failures in under five minutes instead of retrying the same button.
And when a number keeps failing, stop troubleshooting it. Swap the number. A clean number fixes more verification problems than any setting on this list.

