The verification code never arrived — what to do

Updated 5 September 2026 · 6 min read

First, the part that matters most: if no code arrives before the order expires, you are not charged. The price returns to your balance automatically and you do not have to ask. What follows is how to work out why it failed, and what to change before spending again.

What has to happen before a verification code reaches you?

A verification code passes through four parties, and any of them can stop it. Knowing the chain tells you which failures are worth retrying and which are not.

The service decides whether to send. Before anything is transmitted it checks the number you typed against its own rules — the country, the carrier range, how many codes it has already sent to that account. Many refusals happen here, silently.
Its SMS provider routes the message. Large platforms use aggregators that pick a path to the destination network. Routes vary in quality and some drop traffic.
The destination carrier accepts or filters it. Carriers run their own spam filtering on inbound commercial traffic.
We receive it and show it to you. This is the only step we control, and it is rarely the one that fails.

The practical consequence: most non-delivery is decided at step one, before a message exists. That is why waiting longer usually does not help.

Why does an SMS verification code not arrive?

In rough order of how often they actually explain it.

Did the service refuse to send it?

Platforms maintain lists of number ranges allocated to VoIP and verification providers, and many simply refuse them. Nothing arrives because nothing was sent. There is no error shown to you — the signup form just waits. This is the single most common cause, and no amount of patience fixes it.

Have you hit a rate limit?

If several codes have already been requested for that account, that number, or that IP address in a short window, the service may quietly stop sending. The form still behaves as though it worked.

Does the service send to that country?

Some platforms only send to regions where they operate. A number from a country outside that footprint will never receive anything, however good the number is.

Did the carrier filter the message?

Less common, but real: the message was sent and the destination network discarded it. This is the one failure that genuinely sometimes resolves on a retry.

Was the number mistyped?

Worth thirty seconds of checking, including the country code and any leading zero. It happens more often than people admit.

How long should you wait for a code?

When a code has not appeared, work through this in order rather than refreshing hopefully.

0-20 seconds. Do nothing. Domestic delivery is usually near-instant but international routing regularly adds a few seconds, and the order page updates by itself.
20-40 seconds. Re-read the number you pasted into the service, digit for digit. Confirm it matches the one on your order page.
40-60 seconds. Look at whether the service ever acknowledged sending. Most show "code sent" or start a countdown. If it did not, you are looking at cause 1 or 2, and waiting is pointless.
After a minute. Cancel the order — the price comes straight back — and change one variable before trying again. One, not several, or you will not learn anything.

Why do services reject virtual numbers?

Numbers are allocated to operators in blocks, and those blocks are catalogued. A service checking an inbound number can tell, before sending anything, whether it belongs to a range associated with virtual numbers. This is the mechanism behind most silent refusals.

It is also why the operator choice on our order form is not decoration. Where a country offers several carriers, ranges differ in how they are treated: a mainstream national operator generally meets less resistance than an obscure one. If a country fails once, trying a different carrier in the same country is often a better second attempt than jumping to a different country entirely.

Which country should you choose?

The instinct is to pick the cheapest country. The better instinct is to pick the one the service expects.

Platforms serve some markets in volume and barely touch others, and their tolerance for unusual numbers tracks that. A number from a country where the service has millions of users is unremarkable; one from a country where it has almost none stands out before anyone looks at the range. If the account will be used in a particular language or region, matching the number to it is both more likely to work and less likely to attract attention later.

What does a failed verification cost?

Here, nothing. An order that receives no SMS is refunded to your balance automatically, and you can cancel for a full refund at any point before a code lands. You lose the minute, not the money.

This is worth checking on any provider before you fund a balance, because a meaningful share of verification attempts fail through nobody's fault. A service that charges for numbers that never receive anything is charging you for its suppliers' problems. Our rules are in the Refund Policy, in full and in plain terms.

How should you retry after a failure?

Change one thing at a time and stop when you have learned something.

Same country, different carrier. Cheapest test, and it isolates the range rather than the region.
Different country, one the service plainly serves. If this works, the first country was the problem.
If two countries fail in a row, stop. That service is very likely blocking virtual numbers broadly, and no provider will get a code through to you for it. Spending more is throwing good money after bad.

When should you rent a number instead?

If the account matters — anything you will log back into — a disposable number is the wrong choice even when it works. The service will eventually ask you to confirm the number on file, and by then that number belongs to somebody else. An account you cannot re-verify is, in practice, an account you have lost.

For those, rent a number instead: the same number stays yours for 7 to 90 days and receives unlimited messages, so it is still there when the re-verification prompt arrives.