You entered a number, and Telegram either refused it outright or let you request a code that never arrived — now you're staring at "This phone number is banned" or "Too many attempts, try again later." When Telegram won't accept virtual number after virtual number, the app's own error text never tells you which of three unrelated problems you're actually looking at.
That's the core issue with troubleshooting Telegram: the app collapses three separate failure mechanisms into two vague error messages. A number can be rejected because Telegram's carrier-lookup flags it as VoIP. It can be rejected because someone else already ran a Telegram account through that same number before you got it. Or your account request itself can get rate-limited because you (or the number, or the provider's IP range) triggered Telegram's flood-wait system. Each has a different cause and a different fix, and only one of them ("try again in a bit") is actually about waiting.
This article separates the three, decodes the exact wording you're seeing, and tells you which situations need a different number and which just need a timer to run out.
Telegram won't accept virtual number verification? Start here: the three ways it rejects a number
Before you do anything else, figure out which bucket you're in. All three produce a blocked verification, but the fix is different for each.
1. VoIP detection. Telegram checks the number's line type against carrier data before it ever sends a code. If the number resolves as a VoIP or virtual line rather than a real cellular subscriber, Telegram can refuse it or flag the eventual account, sometimes before you've done anything with it. This is not unique to Telegram — most major platforms run some version of this check — but Telegram is known in the community as one of the more aggressive enforcers of it.
2. Recycled-number history. Phone numbers get reassigned. Carriers reclaim inactive lines and reissue them to new subscribers, including SMS-rental providers. If the number you were handed was previously used to register a Telegram account — and that account was later banned, reported, or just abandoned — Telegram's systems may still associate the number with that history. You didn't do anything wrong. The number arrived with baggage.
3. Flood-wait / rate limiting. This one isn't a ban at all. It's Telegram's anti-abuse throttle, and it triggers on repeated actions in a short window — hammering the "resend code" button, switching between SMS and voice-call delivery rapidly, or registering several accounts on the same number back to back. It resolves on a timer. Nothing about the number is wrong.
The mistake most people make is treating all three like the same problem and responding the same way: buy another number, try again immediately, repeat. That works for cause #1 and #2 (sometimes), makes cause #3 worse, and burns money on causes that a five-minute wait would have fixed for free.
"This number is banned" or "too many attempts" — decode the exact wording
Telegram's UI gives you almost no diagnostic information, but the two messages you'll actually see map roughly onto different causes.
"This phone number is banned." This is Telegram telling you the number itself — not an account, the number — is on a block list. This is the message associated with VoIP detection and with recycled numbers that carry a prior ban. It appears immediately, often before Telegram has sent anything, which is your clearest signal that this is a number-level problem rather than something you triggered by your own actions.
"Too many attempts" / flood-wait. This is rate-limiting. It shows up after repeated requests — resending a code multiple times, retrying verification across apps or devices with the same number in quick succession, or a burst of registration attempts from the same IP range. Telegram doesn't publish the exact scaling formula, and duration reports vary by situation — treat any specific number of minutes or hours you read online, including in vendor blogs, as an unconfirmed pattern rather than a documented rule. What's consistent across reports: the wait scales with how many times you keep retrying, and hammering "resend" during the wait extends it rather than shortening it.
If you see "banned" instantly, on a number you've never touched before, that's cause #1 or #2 — no amount of waiting fixes it, you need a different number. If you see "too many attempts" after you've already made several requests, that's cause #3 — a different number might work around it in the moment, but the actual fix is to stop retrying and let the timer run.
Why the error can appear before you've done anything
This is the part that confuses people most, and it's worth stating plainly: Telegram can reject a number on the very first attempt, with zero prior action from you. That's not a bug and it's not Telegram being arbitrary. It's the recycled-number mechanism from a previous owner's history attaching to a number you just received.
Here's the mechanical reason. Carriers don't destroy phone numbers when a subscriber stops paying for the line — they hold it inactive for a cooldown period, then reissue it to someone else. That someone else might be another consumer, or it might be a bulk SMS-rental provider that pools numbers across many customers. If a previous holder of that exact number ran it through Telegram and that account got flagged, banned, or heavily reported, Telegram's records can still carry that association when the number reaches you. There is no publicly available way to check a number's platform history before you buy it — not you, not the provider selling it to you.
This is also the mechanism behind a much broader pattern that isn't specific to Telegram at all: numbers pulled from cheap, high-turnover shared pools fail more often across every verification platform, not because the platform is being unfair, but because more people have already run that exact number through the same check before you did. If you want the fuller mechanism — why this happens on Discord, WhatsApp, and everywhere else too, not just Telegram — see why a fresh number can still get rejected.
Telegram's own attempt limits, explained
Flood-wait is Telegram's own infrastructure protecting itself from abuse, and it treats your registration attempt the same way it treats a bot script hammering the API. The trigger isn't malicious intent, it's request frequency.
Common ways people trip it without meaning to:
- Tapping "resend code" repeatedly because the first one seemed slow
- Switching between SMS and voice call delivery multiple times in a row
- Trying to verify the same number across two apps, or two devices, back to back
- Registering multiple accounts on one number in a short window
The counterintuitive part is that every one of those actions, taken to try to fix a slow delivery, makes the eventual wait longer, not shorter. Telegram doesn't show you a countdown or explain the scaling — you just get told to try again later, with no specifics. Treat any specific duration you see quoted elsewhere as directional, not a promise, since Telegram doesn't publish its rate-limit formula and it can change.
If you're in a flood-wait state right now, the only action that reliably helps is the one that feels wrong: stop requesting. Close the app, don't retry, don't switch numbers mid-window on the assumption that switching resets anything account-side — it doesn't reset the wait tied to that number or session, it just adds a second number to the situation.
Why VoIP numbers specifically get flagged on Telegram
Telegram, like most platforms that rely on phone-based verification as an anti-abuse layer, runs number type checks against carrier data. A real cellular number is tied to an actual mobile subscriber account with a carrier. A VoIP number — Google Voice, Skype numbers, many app-based "second number" services — routes calls and texts through internet infrastructure rather than a cellular network, and that distinction is detectable.
Why does Telegram care? Because VoIP numbers are cheap and easy to provision in bulk, which makes them the tool of choice for large-scale fake-account and spam operations. Telegram's aggressive stance toward VoIP numbers is a direct response to that abuse pattern — it's collateral cost for legitimate users, but it's not arbitrary.
This matters for your fix, not just your understanding: swapping one VoIP number for another VoIP number from a different provider doesn't change the underlying signal Telegram is detecting. The type of number is the problem, not the specific digits. For the full mechanism — how carrier-lookup detection actually works, and why it's the same reason Discord, WhatsApp, and most major platforms behave the same way — see why Telegram flags VoIP numbers specifically.
What actually fixes it
Match the fix to the cause you diagnosed above, not to a generic "try again" instinct.
| If you're seeing... | Likely cause | What actually helps |
|---|---|---|
| "This number is banned," on the first try | VoIP detection or recycled-number history | Switch to a real cellular (non-VoIP) number with no prior Telegram registration |
| "Too many attempts" after several resends | Flood-wait rate limit | Stop requesting; wait it out — a new number doesn't reset the underlying timer if it's tied to your session or IP pattern |
| Code never arrives, no error shown | Delivery failure, often overlapping with VoIP detection | Try a different carrier/operator or country if your provider offers a choice, and confirm the number is real cellular before assuming it's a delivery fluke |
| Rejected instantly, different platforms too | Shared or pooled number, not Telegram-specific | The number itself is the problem, not your Telegram usage — see the broader mechanism |
The structural fix underneath all of this is the same: a dedicated, non-shared, real cellular number with no history on it beats a cheap pooled VoIP number every time you're troubleshooting a rejection. "Dedicated" matters as much as "real SIM" here — a number that's exclusively yours for the rental period hasn't been run through Telegram by five other people before you touched it, which directly removes cause #2 from the equation. A number that's provably cellular removes cause #1. Neither removes cause #3, because flood-wait is about your request pattern, not the number's type or history — but you'll trigger it far less often if you're not repeatedly buying and abandoning rejected numbers in frustration.
If you need Telegram for a business or bot account
If you're setting up Telegram for a support line, a bot account tied to a real business presence, or any use case where you'll be re-verifying, adding devices, or maintaining the account over months rather than once, a one-time number isn't really the right tool. Every re-verification is another opportunity to trip a rate limit or land on a number with unknown history if you're sourcing a fresh number each time.
A long-term rental keeps the same number, and the same clean history on that number, across the life of the account. That matters specifically for Telegram because its abuse-detection systems are widely believed to build up trust signals over time for a given number-account pairing — Telegram doesn't publicly document this, so treat it as an observed pattern, not confirmed policy — and starting over on a new number for every re-verification event forfeits that history, with repeated resets themselves looking like a suspicious pattern to automated fraud systems. If persistent Telegram presence, not a single sign-up, is what you actually need, see keeping the same number for an ongoing Telegram presence for how the rental model works and when it beats paying per verification.
If you're building Telegram verification into a bot or product rather than verifying a personal account, the setup is different — see building Telegram bot verification with our API for the developer-facing integration path.
Frequently asked questions
Why does Telegram say my number is banned when I've never used it?
Because the ban can be attached to the number, not to any account you created. If the number was previously assigned to someone else who registered a Telegram account with it and that account was later flagged or banned, the association can carry over when the number is reissued to you. There's no way to check this in advance — the fix is a different number, ideally one confirmed as real cellular rather than VoIP.
How long does Telegram's flood-wait block last?
Telegram doesn't publish an exact formula, and the duration scales with how many times you've retried in a short window. Community reports describe short waits, sometimes under half an hour, after a handful of quick retries, extending to several hours or longer with repeated attempts. Treat any specific figure as an unconfirmed pattern, not a guarantee — and know that continuing to retry during the wait tends to extend it rather than resolve it faster.
Does Telegram block Google Voice numbers?
Telegram's number-type detection targets VoIP and virtual lines broadly, and Google Voice numbers fall into that category. Community reports describe Google Voice numbers being rejected or flagged on Telegram, consistent with the platform's general stance against VoIP. A real, carrier-issued cellular number avoids this check entirely rather than hoping a specific VoIP provider is currently unflagged.
Can I use the same number for Telegram twice?
Only if the first registration is still active or you deliberately log out and re-register with the same number under your own control. If the number was rented, used once, and released back to a pool, someone else may register a different account on it before you return — at that point it's no longer "your" number in any sense Telegram tracks, and reusing it isn't something you control.
Is renting a number for Telegram against its terms?
Using a rented number to verify a Telegram account you actually control and use legitimately isn't inherently different from using any other phone number for that purpose — Telegram verifies numbers, not their ownership structure. Where this crosses into a genuine problem is bulk account creation, ban evasion, or automated abuse, which Telegram's own systems and terms are built to catch regardless of where the number came from. This describes the general pattern rather than quoting Telegram's current terms directly — read Telegram's own terms of service for the exact current wording.
What's the difference between a delayed code and a rejected number on Telegram?
A delayed code means Telegram accepted the number and is attempting delivery — you'll usually see the request go through with no error, just a wait. A rejected number means Telegram refused it before delivery, typically with the "banned" message appearing immediately. If nothing has arrived after several minutes and there's no error on screen, try the app's SMS-vs-call fallback before assuming the number itself is bad.
Get a number Telegram hasn't seen before
Guessing which cause you're dealing with, and buying another cheap pooled number to test the theory, gets expensive and slow. VerifyPulse sells real cellular, non-VoIP numbers across 184 countries, dedicated to one buyer for the rental period, specifically to avoid the two causes that actually require a different number: VoIP detection and recycled-number history. If a code doesn't arrive, the balance credits back to your account automatically after 20 minutes, or cancelling the number yourself ends the wait immediately — that's a balance credit, not a cash refund; see the refund policy for the separate terms on withdrawing a balance.
Try a real, carrier-issued number with no prior history: start verifying with VerifyPulse.