“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
If you are already signed in to Telegram on any other device — a second phone, a tablet, the desktop app, or Telegram Web in a browser tab — your login code was sent inside Telegram as a message, not by SMS. Check there first. No text is coming, and no fix aimed at your text messages will change that. What follows splits two cases: the code that was never an SMS, and the code that was one and failed. They need different fixes.
Telegram's own documentation is explicit about this, and almost nobody who ranks for the problem quotes it. From telegram.org/faq (read 2026-08-12): “If you have recently used one of our apps on another device (it could also be a different app on the same device), we may send the login code via Telegram instead of SMS.” Read that twice. The message is not late. It was routed away from SMS on purpose, to an app you are already holding.
This is a security feature, not a bug. The most mechanically correct page in these results — a Telegram-account seller we will not link, because it sells the accounts it advises you to protect — gives the clearest reason for it: sending the code in-app rather than by text defeats a SIM-swap attacker, who controls your phone number but not your logged-in session. That reasoning is right. Credit where it is due.
So look for a message, not a text. Open Telegram on every device where you are still signed in and read the chat from the official Telegram service account — the one with the blue checkmark, named Telegram. The code sits in there.
Find it there and that is the whole story: nothing was ever going to arrive by SMS, and every step below is aimed at a problem you do not have.
Now the harder case. You are registering fresh, or you have signed out everywhere, and there is genuinely no other session for Telegram to reach. Only now is a missing code possibly a delivery problem — and even here, three ordinary things account for most of it before the network is worth blaming.
Here is the fix the top guides agree on, and why it fails the reader most likely to need it. Six of the seven pages ranking for this problem tell you to use Telegram's “Call me” option — wait out the SMS timer, then request a phone call that dictates the code aloud. It sounds like a clean fallback.
Telegram's FAQ, same page, read the same day: “For security reasons, login codes dictated via a phone call are only available for accounts that have two-step verification enabled (Settings > Privacy & Security > Two-Step Verification).” Now weigh that against who is asking. A brand-new registration has no two-step verification set up yet — you configure that after you are inside the account. So the single fix repeated across the entire first page of results is, by Telegram's own rule, unavailable to exactly the fresh-registration user it is handed to. Not one ranking page reconciles the two. That is not a small omission. It is the whole first page of results sending its most common reader to a door that will not open.
One more line from the same FAQ, because it explains a silent failure the vendor pages skip: “Please also note that Telegram accounts can only be connected to a mobile number. We currently don't support landline numbers.” (read 2026-08-12). Mobile only. A number that resolves as a landline or a non-mobile line type can be refused with no useful error, and some virtual ranges resolve exactly that way. Why a virtual range gets read as non-mobile is a mechanism worth one place rather than five, and why SMS codes don't arrive is that place.
Now the part where we are conflicted, and will say so in the same breath as the pitch. We rent temporary Telegram numbers. Telegram actively screens the kind of numbers we rent. Both are true at once, and a page that buried the second to sell you the first would be doing the exact thing this site exists to attack.
So the honest position: a rented number may receive a Telegram code, and it may be refused or silently dropped, and we cannot tell you in advance which. What we can hand you is a check you can run yourself in about thirty seconds, before you blame the number. Castle publishes a public blocklist of disposable phone numbers on GitHub — a plain-text file, regenerated daily. Open the raw list and search it for your number in full international form. If it is on there today, a public list already flags it as disposable, and any service that checks a list like this can refuse it on that basis. If it is not, the file rotates tomorrow — so a clean result is a snapshot, not a verdict.
The deeper reason no reseller — us included — can promise you a clean, non-VoIP number is structural. A count of the supplier catalogue behind this market on 2026-07-27 found 161,254 of 165,122 operator rows — 97.7% — sitting in one opaque “virtual…” pool, with only around twenty named operators in the entire catalogue. That is a description of the supply catalogue on a single date, not a success rate for any route. It is also why a per-number “non-VoIP” label from anyone in this business is a label nobody can actually stand behind.
We are free to criticise fabricated statistics precisely because Gate A forbids us from publishing our own — so here are two sitting uncorrected in the top results. On 2026-08-12, lineverifier.com's Telegram page put carrier-level blocking at “15-25% of international verification texts” and pinned “over 40%” of failures on modified apps, both printed beneath a site-wide “99.8% Success Rate” banner (lineverifier.com/blog/telegram-not-sending-code). Neither percentage carries a source or a method — the second is prefaced “I'd estimate … from what I've seen.” They read as precise. They are one author's guess.
The honest version of the same claim is duller and truer. Filtering is real. Its rate is unpublished, it drifts, and anyone printing a tidy percentage for it is guessing. A number with no sample behind it and no window around it isn't a measurement — it's a guess wearing a decimal point.
Four of the pages ranking for this problem quote a specific delivery time. We will not, and the refusal is information rather than a hedge. A verification code you are waiting on is not crossing a wire we own. It passes through the service, an aggregator neither of you chose, the destination carrier, and finally the number — how SMS verification routes fail walks the full chain. We own the last hop and buy a partial view of one more. A number pinned to a stopwatch we cannot see would be a number invented to sound reassuring. The service's own resend timer is the only honest benchmark on your screen: it encodes what Telegram expects from its own sender, which is more than an outsider can measure.
Which brings us to the most honest thing we can put on a page about renting a Telegram number: today, we have measured nothing. Every route on this site renders the same sentence rather than a number we cannot back:
We don't have data for this route yet
That is not modesty and it is not a soft launch. It is the designed state. We publish a success rate for a route only after we have counted it from our own completed orders, with the sample size and the window shown beside it — and we have taken no orders. So for your case, the truthful answer to whether a rented number will get your Telegram code is that we do not yet know, and this route may simply not work for you. When ordering opens, the Telegram number page is where it will be, and it renders that same NO DATA state until a real measurement replaces it. If you are weighing whether a rented number is the right tool at all, is it safe to use a virtual number is the more useful read first, and do you need a phone number for Telegram covers whether you need a separate number here in the first place.
No. If any other Telegram session is active — another phone, the desktop app, or Telegram Web — Telegram sends the login code as an in-app message instead of a text, by its own documentation (read 2026-08-12). Read the Telegram service chat on those devices before you treat it as a delivery failure.
No. telegram.org states that call-dictated login codes “are only available for accounts that have two-step verification enabled” (read 2026-08-12). A fresh registration has not set that up yet, so the call option so many guides recommend is not offered to the exact user they are advising. Wait the resend timer out instead.
Possibly, and possibly not — we cannot tell you in advance. Telegram supports mobile numbers only and screens ranges it reads as non-mobile. Check the number against Castle's public disposable-number list (linked above), and read why SMS codes don't arrive for the line-type mechanism. Our own Telegram routes carry no measured data today.
Sometimes. Telegram has added email-based login codes and passkeys since most troubleshooting guides for this problem were written, and on some accounts an email code is offered as an alternative to the phone code. If your account shows the option, it sidesteps the SMS path entirely.
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.