It is one of the most frustrating experiences in the digital world: you enter your phone number, click 'Send Code,' and... nothing. You wait 30 seconds, a minute, two minutes. Still nothing. You click 'Resend' and wait again. Nothing. What is happening?
OTP non-delivery is far more common than most people realize. Studies show that 15–25% of legitimate SMS verification attempts fail on the first try globally. The causes range from carrier-level routing problems to platform-side rate limits to simple user errors. This guide walks through the 7 most common causes and provides an actionable fix for each one.
#How SMS Delivery Actually Works (And Where It Can Fail)
Understanding the SMS delivery pipeline helps identify where failures occur. When a platform sends you an OTP, the message passes through 4–6 intermediaries:
Platform triggers SMS
The platform's backend calls their SMS gateway API (e.g., Twilio, Vonage, MessageBird) with your phone number and the OTP code.
SMS gateway processes the request
The gateway validates the number format, checks for blocklists, selects a routing path, and sends the message into the telecom network.
Carrier network routes the message
The message passes through one or more carrier networks via SS7 signaling until it reaches the carrier that owns your phone number.
Destination carrier delivers to your device
The final carrier delivers the SMS to the device (or virtual number dashboard) associated with the phone number.
A failure at any point in this chain results in no code arriving. Let us examine each common failure mode:
#Cause 1: You Are Using a VoIP Number
Symptom: You enter the number, the platform says 'code sent,' but nothing arrives. Or the platform immediately rejects the number with 'not supported.'
Why it happens: The platform checks the number's carrier classification and finds it is VoIP. It either silently drops the SMS or outright rejects the number.
Fix: Use a non-VoIP (real carrier) number from Shadow SMS. The number will be classified as 'Mobile' in carrier databases and pass the check.
#Cause 2: IP Address / Country Mismatch
Symptom: The platform shows a generic error like 'something went wrong' or the code is sent but the account creation fails at a later step.
Why it happens: Your IP address is in a different country than your phone number. Platforms like Google, WhatsApp, and Instagram flag this as suspicious.
Fix: Use a VPN or proxy matching the country of your phone number. If you have a US number, use a US IP. Residential proxies work best.
#Cause 3: Platform Rate Limiting
Symptom: 'Too many attempts. Try again later.' or codes simply stop arriving after several tries.
Why it happens: You have clicked 'Send Code' too many times in a short period. The platform's rate limiter has blocked further SMS deliveries to prevent abuse.
Fix: Wait. Rate limit cooldowns vary: WhatsApp is 12–24 hours. Google can be 24–72 hours. Instagram varies. Do not keep clicking resend — each failed attempt extends the cooldown.
#Cause 4: Carrier-Side SMS Filtering
Symptom: Codes arrive for some services but not others from the same phone number.
Why it happens: Some carriers apply aggressive spam filtering that can intercept legitimate verification SMS. This is more common with certain carriers in certain countries.
Fix: Try a number from a different country or carrier. Shadow SMS sources numbers from multiple carriers, so requesting a new number often resolves carrier-specific filtering issues.
#Cause 5: Number Was Recently Used for the Same Service
Symptom: The platform says 'this number has already been used' or 'this number is associated with another account.'
Why it happens: The number was recently used by another user to verify the same platform. The platform recognizes the number and rejects it.
Fix: Cancel the current number and request a new one. Shadow SMS has a large number pool, so the next number will be fresh for your target platform.
#Cause 6: Wrong Number Format
Symptom: 'Invalid phone number' error or the platform does not send a code.
Why it happens: You entered the number in the wrong format. Some platforms want the full international format (+1XXXXXXXXXX), while others want just the local number without the country code.
Fix: Try both formats. If the platform has a country code selector, match it to your number's country and enter only the local digits. If there is no selector, enter the full international format including the + prefix.
#Cause 7: Platform SMS Gateway Outage
Symptom: Nobody is receiving codes from this platform — not just you.
Why it happens: The platform's SMS gateway provider is experiencing an outage. This is surprisingly common — Twilio, Vonage, and other major SMS gateways have had multiple outages in recent years.
Fix: Wait 30–60 minutes and try again. Check DownDetector or the platform's status page to see if others are reporting the same issue.
#Frequently Asked Questions
Jane Parkins
AuthorPrivacy & Telecom Analyst specializing in privacy engineering, telecom infrastructure, anti-bot protocols, and identity security.
Need a Virtual Number Right Now?
Get an instant OTP verification number across 50+ countries. Only pay for successful activations.
