Frozen, restricted, banned, flood-wait: Telegram account triage
Four account states, four different problems. A mid-incident reference: what each state still allows, which ones clear on their own, and the first move for each - starting with the two you can make worse.
Updated: August 2026 · 7 min read
Naming the state precisely is the first job of any Telegram account incident. FloodWait, a spam restriction, FROZEN and a ban look alike from the outside - actions fail - but they differ in what still works, whether they clear on their own and how much the wrong reaction costs. Two of the four get worse if you push.
Start with triage
Identify the state from the exact symptom, then make the first move for that state - nothing else. The most useful diagnostic is messaging @SpamBot from the affected account: it says whether the account is limited, what is blocked and, for temporary limits, until when.
| State | What still works | Clears on its own? | First move |
|---|---|---|---|
| FloodWait | Everything - the error says how long to wait | Yes - a rate limit, not a penalty | Wait out the full timer, then slow the schedule that caused it |
| Restricted (spam-limited) | Reading, channels, messaging existing contacts | Usually - @SpamBot shows the expiry | Ask @SpamBot what is limited; appeal there; stop messaging non-contacts |
| FROZEN | Login and reading only - no writing, joining or profile edits | No - and the recovery window is short | Recover via the spam bot with a trusted-device confirmation - same hour |
| Banned | Nothing - the number is rejected at login | No - terminal | Appeal via the address in Telegram's FAQ; find the cause before replacing |
FloodWait: a rate limit, not a penalty
FloodWait is Telegram's server-side rate limit: call a method too often and the call fails with an explicit wait time in seconds. It is transient and self-healing: sit out the timer and the account continues as before. There is no appeal, because there is nothing to appeal.
The only way to make it worse is to retry harder: hammering a method already in flood-wait is how a 30-second wait escalates into hours. Treat the returned wait as a minimum, and fix the schedule that produced the burst, not the failed call.
An uncapped overnight search pass in our own fleet flood-waited the account by morning, and the fix was scheduling rather than retry logic - caps and windows.
Restricted: spam-limited but alive
A restriction - @SpamBot calls it being “limited” - is Telegram's response to reports about unwanted messages. The account keeps most of its life: reading everything, posting where it already belongs, messaging existing contacts. What breaks is initiating: starting chats with people outside your contacts, and inviting strangers to groups.
@SpamBot states what is limited and until when; if you believe the limit is a mistake, the appeal runs through the same bot. A first restriction on a clean account typically expires on schedule. Repeat restrictions are widely reported to get longer each time - Telegram does not publish the schedule, so treat that as operator experience, not a documented rule.
Operationally: stop all outbound to non-contacts at once, keep the read-only work running - chat monitoring is unaffected - and find out what got the account reported before the pattern repeats on its siblings.
FROZEN: read-only, on a deadline
FROZEN is the harshest state short of a ban. By consensus of secondary sources it appeared around May 2025; we found no primary Telegram announcement, so treat the details as community-verified, not official. What is consistently reported and matches what we have seen: a frozen account still opens and reads, but cannot write, join anything or edit its profile - fully read-only.
Recovery runs through the spam bot and requires confirmation from a trusted device - an existing logged-in session. Miss the window and the account is deleted, irreversibly. The widely quoted figure of about 24 hours is not officially confirmed - an argument for moving faster, not slower.
A freeze does not require misbehaviour: two day-0 accounts on Iranian numbers in our own fleet were frozen before any automation had touched them - the numbers' origin was enough (more below). When it happens, the dashboard latches the account as frozen, stops all activity on it and fails actions with an explicit “account frozen” error instead of a timeout.
Banned: the sticky end state
A ban is terminal: the number is rejected at login; for your fleet the account is gone. Telegram's FAQ lists an email for banned-number appeals - recover@telegram.org at the time of writing, verify on telegram.org/faq - but for numbers banned around spam-like behaviour, reinstatement is nothing to plan around.
The useful work after a ban is forensic: which cause below applies, and does it touch the fleet - same number batch, same proxy subnet, same schedule? If the account was bought, its history was never yours to audit: what you inherit with a purchased account is a lottery. A ban that teaches you nothing tends to repeat.
Why it happens, ranked by how often it bites
Ranked by how often each cause actually takes accounts down in practice:
- Number origin and country risk. Some numbers are burnt before the first login: carriers that block Telegram, filtered SMS codes and leaked identifier sets make whole countries of origin suspect - the evidence, country by country, is in choosing phone numbers. That is how the two day-0 freezes above happened.
- Proxy and geo mismatch. The account's country comes from its phone code; its network story comes from the proxy exit. Scoring notices when the two disagree - and a session whose exit IP or network changes mid-flight looks hijacked, which is why rotating residential or mobile proxies are the wrong product here.
- Bought-account history. Marketplaces mix honestly registered accounts with phished and stolen ones, and some label lots by origin in their own API - the labels are in the buying guide. The first thing a buyer does - new device, new IP, instant activity - is precisely the takeover pattern anti-abuse systems exist to catch.
- Behaviour spikes. Day-0 bursts: dozens of joins, searches every few seconds, messaging from an account with no history to justify any of it. New accounts are judged on thin evidence - build history before workload.
- Mass reports from recipients. The classic road to restriction: messaging people who did not ask. Enough recipients tap Report and the limit follows - correctly. No tooling fixes this, only restraint: low volume, and only messages the recipient would plausibly welcome.
Prevention checklist
No checklist eliminates risk - anyone promising that is selling something. It removes the causes you inflict on yourself - in practice, most of them:
- One account, one static proxy, geo matched to the number's country. Sticky per-account exits, never rotating pools - how to choose proxies for Telegram.
- Numbers you registered yourself, from countries you can also buy proxies in, never from high-risk origins - choosing phone numbers for Telegram.
- History before workload. A quiet human routine - join, read, rest - with daily caps and quiet hours in the account's own timezone: account warming.
- One driver per authorization. Several authorizations are normal - a phone, a desktop and one automation tool each hold their own key. What breaks accounts is two programs driving one and the same key at once: Telegram can invalidate it and log both sides out. Move accounts with a proper tdata or session-string import rather than a second login.
- A unique, non-default device fingerprint per account, set once and never changed. Defaults and duplicates cluster your fleet into one recognisable blob.
- Caps on everything outbound, with a separate slow lane for search actions. If you run outreach, keep it opt-in and small - Teleliner's ceiling is 10-30 first contacts per day per account depending on plan, deliberately.
- Watch FloodWait frequency as a leading indicator. Rising flood-waits are the cheapest early warning you will get - slow the account down before Telegram does it for you.
Frequently asked questions
How long do I have to unfreeze a FROZEN account?
Officially unknown. Secondary sources widely quote about 24 hours, but Telegram has not confirmed it, and we found no primary announcement of the FROZEN state at all. Treat it as a same-hour incident: confirm through the spam bot from a trusted device immediately, because a missed window ends in irreversible deletion.
Is a FloodWait a strike against my account?
Not by itself - it is a transient rate limit that expires on its own. The danger is your reaction: retrying before the timer runs out escalates the wait. Frequent flood-waits are still worth acting on, as a sign the account's schedule is too aggressive.
How do I check whether my account is restricted?
Message @SpamBot from the account itself. It replies with the current status: whether the account is limited, which actions are blocked, and the expiry date for temporary limits. Appeals run through the same bot.
Does a restriction stop read-only monitoring?
No. A spam-limited account still reads chats and channels normally; the restriction blocks initiating contact with non-contacts. Read-only work such as chat monitoring continues - one reason to keep monitoring and outreach on separate accounts.
Can a banned number be recovered?
Telegram's FAQ lists an appeal address for banned numbers - recover@telegram.org at the time of writing; verify on telegram.org/faq. In practice, for numbers banned around spam-like activity, plan for replacement - and work out what caused the ban before pointing a new account at the same proxy and schedule.
Why was my account frozen on day 0, before I did anything?
Number history. A number can be burnt before the first login: a high-risk country of origin, presence in leaked databases, or a previous life you cannot see - a standard risk with purchased accounts. That is what happened to the two accounts described under FROZEN.