If your OTP is not received, the cause is almost always in one of three places: the number you typed, your phone's own filters, or the sender and carrier between you. Spend three minutes working out which one before you tap "Resend" again, because repeated resends can lock you out for longer. Below are the eight most common causes, a quick test for each, and the fix. If you'd rather watch, the same causes are covered in our two-minute video on missing OTP codes.
We run NumberOTP, a service that sells private numbers for receiving verification codes. Most of this guide applies to your own SIM and costs nothing to fix.
OTP not received: the three-minute check
Start by sorting the problem into one of three buckets. Each test takes under a minute and tells you where to look next.
| Test | If it fails | Likely bucket |
|---|---|---|
| Ask someone to text you a normal SMS | No SMS of any kind arrives | Your phone, SIM or plan |
| Normal texts arrive, but no codes from any app | Only short-code or sender-name messages are missing | Filters on the phone or carrier blocking |
| Codes from other apps arrive, but not from this one | One service never reaches you | The number entered, rate limits, or the sender |
| Put your SIM in another phone and request once | The code arrives on the other phone | Your handset or its settings |
The SIM-swap test is one that many guides skip, and it is the fastest way to stop blaming the app when the handset is the problem.
1. The number is written wrong
A wrong country code or an extra leading zero is the most common reason a code goes nowhere. The app happily "sends" the code to a number that isn't yours, or rejects it silently.
- Pick the country from the dropdown, then type the national number without its leading 0 (a UK number starting 07 becomes 7…).
- Don't type the country code twice: if the field already shows +44, don't add 44 again.
- Paste the number into a free phone number formatter to see it in international form before you submit.
Developers hit the same issue from the other side: we cover the exact patterns in the E.164 formatting mistakes that break SMS verification.
2. You resent the code too many times
Pressing "Resend" five times rarely helps and often makes things worse. Most services throttle repeat requests, and each new request cancels the previous code.
Google states in its 2-Step Verification help that if you request several codes, only the newest one works. Its account-recovery help also mentions a daily limit on code requests, after which you have to wait 24 hours. Other services behave similarly, even when they don't publish the numbers.
Fix: request once, wait two or three minutes, then resend once. If a "Call me" or voice option appears, use that instead of a third text.
3. The code expired before you typed it
OTP codes are short-lived by design, and a code that arrives late may already be dead. If you typed a code and got "invalid" or "expired", the code probably wasn't the problem: its timing was.
Always use the newest message in the thread, not the first one you see. If you switch apps to read the SMS and the sign-in page reloads, the page may have requested a fresh code in the background. Our guide to how one-time codes work explains why they expire so quickly.
4. Your phone filtered or hid the message
The code often did arrive, but your messaging app put it somewhere you aren't looking. This is the most common cause when normal texts work fine.
iPhone: Screen Unknown Senders
Apple's support article on unknown senders (published April 2026) explains how iOS 26 handles this. Screen Unknown Senders is off by default, but it stays on if you had Filter Unknown Senders enabled in iOS 18. Notifications for Time Sensitive messages, such as verification codes, are on by default. Allowed messages show in your main list for eight hours, then move to the Unknown Senders area. Check there first.
- Open Messages, tap Filters and look in Unknown Senders.
- To change it, go to Settings → Apps → Messages → Unknown Senders.
- Apple notes that filtering doesn't apply to senders you've replied to three or more times. Short codes can't take replies, so marking the sender as known is the more reliable fix.
Android: Spam & blocked
In Google Messages, conversations reported as spam go to the "Spam & blocked" folder, which you open from the profile menu. If you once reported a bank or app sender as spam, every later code from it lands there. Other Android messaging apps have their own spam or "promotions" folders.
Also check
- Do Not Disturb or Focus modes that silence notifications (the message is there, you just weren't told).
- A third-party spam filter app or a carrier "block unknown senders" feature.
- Full device storage on older phones, which can stop new SMS from saving.
5. No signal, roaming or a plan problem
SMS needs a working cellular connection, and Wi-Fi alone usually isn't enough. If no texts arrive at all, the problem is the line, not the app.
- Toggle airplane mode off and on, or restart the phone. Google's help suggests a restart and, if that fails, asking your carrier to reset text messaging settings.
- When abroad, check that roaming is enabled for your SIM. Some prepaid plans block incoming SMS from abroad or when the balance is zero.
- If you recently moved your number to a new carrier, codes can fail for a while until the transfer settles everywhere.
6. The app won't send codes to your type of number
Some services check the line type before sending and refuse VoIP or app-based numbers. The sign-up form may show an error, or it may just never send the code.
If you're trying to receive codes on a Google Voice, TextNow or similar number, this is the likely cause. Run the number through a carrier and line-type lookup to see what apps see. We explain how apps tell a VoIP line from a mobile line in a separate post. Some services also publish lists of country codes they can't deliver codes to. In October 2026, for example, one fintech's help centre listed thirteen of them, so check the service's own help page if you're using a foreign number.
7. The carrier filtered the message
Carriers block messages they think are spam, and verification texts get caught too. Sometimes the carrier blocks short codes entirely on your account.
From the sender's side this is visible: Twilio's documentation for error 30007, "Message filtered" says the message was blocked by Twilio or by the carrier. You can't see that error as the recipient, but you can act on it.
- Ask your carrier whether short codes or premium messages are blocked on your line, and to unblock them. Google's help gives this as a fix too.
- Use the voice call option or another sign-in method (email, authenticator app, passkey) if the service offers one.
- If you send codes yourself, log the delivery status for every message. Our Node.js webhook walkthrough shows one way to capture what really happened to each code.
8. The service itself is having trouble
Sometimes nothing is wrong on your end. Services have outages, and Google says delivery can be delayed in busy places or during carrier issues.
If the three-minute check points to the sender, wait 10 to 15 minutes, then try once more, ideally with the call option. Check the service's status page or social account before you change settings on your phone.
What not to do
A few common "fixes" cause new problems. Avoid these.
- Resetting network settings first. It erases saved Wi-Fi networks and Bluetooth pairings and isn't a targeted fix for SMS. Try it only after a restart and the carrier check.
- Using a free public number for your own account. Anyone can read codes on free temporary number sites, and those numbers are usually blocked by the apps anyway.
- Sharing the code with anyone who asks. No real support agent needs your one-time code. If a code arrives that you didn't request, don't forward it.
When a second number is the real fix
If your own SIM keeps failing for one service (abroad, on a plan that blocks short codes, or because you don't want to give that service your main number), a separate number for receiving codes can solve it. We cover the options in our guide to getting a second number without a new SIM.
NumberOTP numbers are real SIM-backed mobile numbers from three independent number pools on our own infrastructure, rented for one code or for longer. As of 22 November 2026, our refund policy says that if no SMS arrives within the activation window (typically 20 minutes), that activation is credited back to your wallet automatically. Use it for your own accounts and follow each platform's terms; some platforms don't allow virtual numbers. A number usually works with a given app, but no service can promise that every platform accepts it.
Frequently Asked Questions
Why am I not receiving OTP codes when normal texts arrive?
When normal texts arrive but codes don't, the code is usually being filtered rather than lost. Check your messaging app's unknown-sender or spam folder first, then ask your carrier whether short codes are blocked on your line. If codes from other apps arrive fine, the problem is specific to that one service: the number you entered, its rate limits, or its sender.
How long should I wait before resending an OTP?
Wait two or three minutes before you request a new code, then resend only once. Many services throttle repeated requests, and each new request usually cancels the previous code, so tapping resend repeatedly can lock you out for hours. If the service offers a voice call option, use that for your second attempt instead of another text message.
Why does my OTP say invalid even though I typed it correctly?
The most likely reason is that you typed an older code. When you request several codes, most services accept only the newest one, and codes expire within minutes. Close the sign-in page, request a single fresh code, and type the latest message in the thread. Also check that the page didn't reload and request a new code while you were reading your messages.
Can my phone block OTP messages without telling me?
Yes. On iPhone, Screen Unknown Senders can move messages from senders not in your contacts out of the main list, and on Android, a sender you once reported as spam goes to the Spam and blocked folder. Focus or Do Not Disturb modes can also hide the notification even though the message arrived. Check those folders and settings before blaming the service.
Will a virtual number fix OTP codes that never arrive?
It can, when the problem is your own line, such as roaming, a plan that blocks short codes, or not wanting to share your main number. It won't help if the service rejects non-mobile numbers or blocks the country you choose. Use a private, SIM-backed number rather than a free public one, use it only for your own accounts, and pick a service that refunds activations when no SMS arrives.
Get the code, or get your money back
Work through the three-minute check first: most missing codes are fixed by entering the number correctly, waiting before resending, or checking a filtered folder. If your own SIM still can't receive codes for a service, create a free NumberOTP account and pick a private number for that service. If no SMS arrives, the activation is refunded to your wallet automatically.
Frequently Asked Questions
Why am I not receiving OTP codes when normal texts arrive?+
When normal texts arrive but codes don't, the code is usually being filtered rather than lost. Check your messaging app's unknown-sender or spam folder first, then ask your carrier whether short codes are blocked on your line. If codes from other apps arrive fine, the problem is specific to that one service: the number you entered, its rate limits, or its sender.
How long should I wait before resending an OTP?+
Wait two or three minutes before you request a new code, then resend only once. Many services throttle repeated requests, and each new request usually cancels the previous code, so tapping resend repeatedly can lock you out for hours. If the service offers a voice call option, use that for your second attempt instead of another text message.
Why does my OTP say invalid even though I typed it correctly?+
The most likely reason is that you typed an older code. When you request several codes, most services accept only the newest one, and codes expire within minutes. Close the sign-in page, request a single fresh code, and type the latest message in the thread. Also check that the page didn't reload and request a new code while you were reading your messages.
Can my phone block OTP messages without telling me?+
Yes. On iPhone, Screen Unknown Senders can move messages from senders not in your contacts out of the main list, and on Android, a sender you once reported as spam goes to the Spam and blocked folder. Focus or Do Not Disturb modes can also hide the notification even though the message arrived. Check those folders and settings before blaming the service.
Will a virtual number fix OTP codes that never arrive?+
It can, when the problem is your own line, such as roaming, a plan that blocks short codes, or not wanting to share your main number. It won't help if the service rejects non-mobile numbers or blocks the country you choose. Use a private, SIM-backed number rather than a free public one, use it only for your own accounts, and pick a service that refunds activations when no SMS arrives.
Need a number right now? Get $0.10 in free credits — no card required.
Sign up free →Written by
Nanami
Nanami is a telecom and digital privacy specialist at NumberOTP with over 8 years of experience in SMS verification systems, virtual phone infrastructure, and online identity protection. He covers OTP security, number masking, developer APIs, and privacy-first verification workflows for businesses and developers worldwide.
Get your first OTP number free
$0.10 in credits on signup. No card required. Works for 800+ platforms.