“This phone number cannot be used for verification”
Google returns this before it sends anything. It can mean four things — a flagged account, an undisclosed account quota, the line type, or the format.
Pre-launch — you can read everything, but ordering isn't open yet. Where we are
An Instagram code that isn't arriving has one of three causes, and each needs a different fix. The fault is in your handset, in the route the number rides, or in a hold Instagram has placed on the account itself. One test tells you which. Request the code again on a different number and a different network — if it still fails, the problem is not your phone.
This is the diagnostic, not the setup. If you rented a number here and the code won't come, the country selector is the usual culprit, and our Instagram number guide already walks that check — set the country to match the number before anything else. What follows is for the failure that survives that fix.
Change one variable at a time. A code request that keeps failing across a different number, a fresh network and a second handset cannot be coming from your own phone — you have ruled the whole first layer out. Keep that result. It decides everything below, because a route problem moves when you move the number, and an account problem does not move at all.
You can run the handset half of that without spending anything. Toggle from Wi-Fi to mobile data and request the code again. Try a second device signed into the same account. Move off Do Not Disturb. If nothing appears after all of that, the first layer is clean and the fault is riding the number or the account — which is the split the rest of this page is about.
The cheapest layer to clear, and the one every generic troubleshooting page stops at. Work through what your own phone can be doing to a text before it ever reaches the screen:
None of that costs a number, ours or anyone's. If the code appears once you've cleared these, you were never in the delivery problem people assume this is — and you can stop reading here.
The handset is clean and the code still won't come. Now the number matters — the carrier and range it belongs to, which Instagram inspects before it decides whether to send at all.
Instagram screens line type at that step, and virtual and VoIP ranges are commonly refused there; on top of that sits the carrier-level A2P filtering that quietly drops verification traffic. Whether a given range is clean is close to unknowable from outside. When we counted our supplier's own operator catalogue on 2026-07-27, 161,254 of 165,122 rows — 97.7% — carried no operator name at all, only an opaque "virtual" label. That mechanism, and why the opacity defeats any per-range promise, is why SMS codes don't arrive — it gets one paragraph here because that page owns it.
A route problem has a clean signature: swap in a fresh number and the code lands. That is the whole point of renting from a pool — if Spain's ranges are being refused today, Estonia's may not be. The route-level view of why a supply pool goes stale is in how SMS verification routes fail.
The hardest case, and the one a new number cannot touch. Here Instagram is not failing to deliver a code — it has decided not to issue one. The request looks identical from your side, which is exactly why people burn money renting number after number against it.
The prior-holder case is worth naming, because it stays invisible until it bites. A recycled number can reach you already attached to a stranger's old signup, so the code meant to confirm you confirms someone else's account instead. We say plainly in our terms that pool numbers are recycled and what that means — it is a property of every pool, ours included, not a flaw unique to one supplier.
The test from the top settles it. If a fresh number that receives other codes fine still gets nothing on this account, you are in layer three. The fix is Instagram's review flow — not us, and not a different range. Renting again would be money spent on the wrong layer.
One option the panic skips: Instagram offers more than SMS. Setting up its two-factor step, Android Authority records the exact prompt — “Hit SMS or WhatsApp and follow instructions to finish the set-up” (read 2026-08-12). A WhatsApp code travels over data, not the SMS network, so it routes around the A2P carrier filtering that eats verification texts. You need WhatsApp installed on a number you actually control. It is not a universal escape hatch: if the account is stuck in layer three, the WhatsApp option is gated behind the same review. For a plain delivery failure, though, it is the cheapest thing to try — it costs nothing.
If your answer is a fresh number and you're weighing where to rent one, here is the honest part. We are new. On most routes we have placed no orders of our own, so we publish no reliability figure — the page says the true thing instead:
We don't have data for this route yet
That holds for the popular routes as much as the quiet ones. A brand-new site posting a confident success rate on every country would be inventing them, and conspicuously empty beats quietly wrong. Every price and route state is readable without an account on pricing, and the labelling rules — measured, supplier-reported, or the sentence above — are on the trust page. The countries we carry are on the Instagram numbers page.
Two very different failures share that message. Either the carrier or Instagram refused the number's range — layer two — or the account is under a hold and no number will clear it — layer three. Run the fresh-number test to tell them apart before you spend anything.
Only in layer two. A new number on a different route steps around a refused range or a filtering carrier. It does nothing for a handset setting or an account checkpoint, which is why the test at the top earns its place first.
Often, yes. Instagram's two-factor setup lists WhatsApp beside SMS (per Android Authority, read 2026-08-12), and a WhatsApp code rides data rather than the SMS network, so it dodges the A2P filtering that drops texts. The catch is the obvious one: you need WhatsApp on a number you control.
Work the layers in order — handset, then route, then account — and stop at the one where a change fixes it. If a route is refusing you, another route may not, so switch numbers before you switch anything else. Every price and route state here is public, so comparing before you re-order costs nothing. Failure is per route, not per number: a number invisible to Instagram today can be ordinary to another service on the same afternoon.
Every route shows its price and its data state up front — and where we have nothing yet, it says so.
Every route below is one click away. Open a country to see its services, or jump straight to a service hub.