Most pages on this topic treat every refusal from Telegram as one thing called a ban. That is why the advice attached to them so often fails. A wait of 37 seconds on a message send, a login screen that says the number asked for too many codes, a bot that gets 429 back from the Bot API and an account that suddenly cannot write to strangers are four separate mechanisms. They have different names, different timers, and only some of them are documented.
The useful question each time is which counter tripped. The answer is usually in the error text, and the rest of this article reads it layer by layer.
What is flood wait in Telegram?
Telegram's API error reference files it under error 420, FLOOD, which it defines as the maximum number of attempts to call a given method with the given parameters having been exceeded. The specific form is FLOOD_WAIT_X, described as a wait of X seconds being required. So the flood wait telegram meaning is narrow and precise: this account, calling this method, has to pause for X seconds. It is telegram flood control working as designed, not a judgement on the account.
Three details follow from that definition. The counter is tied to a method, so an account waiting on message sends can often still read chats or change settings. It is tied to the account, so a second account is not affected by the first one's wait. And X is stated in the error itself, so a telegram flood wait always tells you its own length and the telegram flood wait time is never a mystery to the code that receives it. It can be a few seconds or many hours, and nothing published says how Telegram picks the number.
The same limit under different names
People search for it as flood_wait telegram, copied straight from a log, or as telegram floodwait when the library joins the words, as Telethon's FloodWaitError and Pyrogram's FloodWait do. It is all one error. The Telethon documentation says the library sleeps through waits shorter than 60 seconds by default and raises the error for anything longer, which is why a script can look slow for a while before it finally stops. Telegram also lists FLOOD_PREMIUM_WAIT_X, a wait applied to transfer speed on accounts without Premium, and it is the only flood wait the reference says Premium removes. Bulk work such as copying every file out of a channel meets that one most often.
Phone number flood is a login limit
Phone number flood telegram errors appear before an account even exists in a session. The auth.sendCode method page lists PHONE_NUMBER_FLOOD as "You asked for the code too many times." It counts code requests for one number, not messages, so waiting is the only route back, and asking again from another app keeps the counter running rather than resetting it. Its neighbour, PHONE_PASSWORD_FLOOD, counts failed two-step password attempts. Neither one says anything about whether the account sends spam. They mean the login was tried too often.
Five errors that look alike, read side by side
Here are the refusals that get grouped under telegram rate limits, with what each one counts. The first column is the name you will see in a log or a library exception.
| Error | Who gets it | Timer stated? | What it counts | What fixes it |
|---|---|---|---|---|
| SLOWMODE_WAIT_X | Accounts writing in a group | Yes, X seconds | Slow mode set by the group's admins | Wait, or post less often in that chat |
| FLOOD_WAIT_X | Accounts and bots on MTProto | Yes, X seconds | Repeated calls to one method | Wait the full X, then slow the loop |
| 429 Too Many Requests | Bots on the Bot API | Yes, retry_after | Per-chat, per-group and global send rates | Wait retry_after, then queue sends |
| PHONE_NUMBER_FLOOD | Anyone logging in | No | Login code requests for one number | Stop requesting codes for a while |
| PEER_FLOOD | Accounts writing to strangers | No | Not defined in Telegram's public reference | Stop first messages; check SpamBot |
Read down the third column. Everything with a timer is a rate limit, and it clears by itself. The two rows without one are different in kind. PHONE_NUMBER_FLOOD clears on its own schedule. PEER_FLOOD does not appear in Telegram's own error list or on the messages.sendMessage page at all, and every explanation of it comes from library authors and tool vendors. In practice it shows up when an account sends first messages to people who do not know it, and it tends to travel with the spam restriction described further down. Treat it as the account's status speaking, not a counter that will reset in a minute. Anyone searching peer flood telegram after a telegram flood wait has already cleared is usually looking at this second problem.
Is there a Telegram message limit per day?
Not one that Telegram publishes for user accounts. As of October 2026 there is no official telegram message limit per day, no telegram dm limit, no telegram send message limit and no telegram send limit stated anywhere on telegram.org or core.telegram.org. Figures that circulate, such as a set number of new chats a day for a new account and a higher one for an aged account, come from vendors and forums describing what they saw. They are useful as observations and wrong as policy, and Telegram can change the behaviour behind them without notice. When a page quotes a daily telegram message limit as a rule, ask for the source.
What does exist is documented for bots, and for one or two individual methods. The phone lookup a number check relies on is documented at one call every three seconds, for instance, which is unusual. The registration month a first message reveals is the closest public signal of how old an account is, and age is the variable most of those community figures hinge on. A telegram message limit exceeded warning in a third-party tool is usually that tool's own cap, not Telegram's.
Bot limits and the 429 error
Bots are the one place where numbers are official. The Bots FAQ asks bot developers to avoid more than one message per second in a single chat, no more than 20 messages per minute in one group, and about 30 messages per second for bulk notifications, spread over several hours for a large audience. Go past those and the Bot API answers telegram 429 too many requests. That telegram bot too many requests reply carries a parameter whose meaning the Bot API reference gives as "the number of seconds left to wait before the request can be repeated" in case of exceeding flood control.
So when a dashboard shows telegram too many requests retry after 35, the fix is literal: wait 35 seconds and send the same request once. Telegram too many requests try again later means the same thing without the number. Retrying in a tight loop is the most common way a short wait becomes a long one. Above the free rate, paid broadcasts let a bot send up to 1,000 messages per second for 0.1 Stars each, and the FAQ and the API page give different Star balances for who qualifies, so check both before planning around it.
None of these bot figures applies to a user account. Bots also cannot write first. A user has to start the bot, and pressing the Stop button in a bot chat is the same as blocking it, so a bot that floods its users simply loses them.
Why is my Telegram account restricted for no reason?
Usually because enough people reported messages from it, or because something about the number looked like spam before it sent anything. Telegram's spam FAQ covers both cases. Reports lead to a limit. New accounts can be limited too, and the FAQ names reasons such as numbers from virtual phone services or a number's previous owner having been reported. It also admits plainly that its systems make mistakes. That is the honest answer to telegram account restricted for no reason: there was a reason in Telegram's data, even if it was not your doing.
A telegram spam block, or telegram spam restriction, has a published shape. A limited account can send messages only to people who have its number saved as a contact, and it can always reply to anyone who writes to it first. Adding people to groups narrows the same way, and the apps tell a limited account that it can only add mutual contacts for now. If putting your saved contacts into a group suddenly fails for every name, that is often the reason. A first offence typically lasts a few days, and repeated offences mean longer blocks.
Telegram account restricted vs banned
A telegram account restricted this way still logs in, reads, and talks to people who saved it. A banned account does not log in at all. The two get confused because outreach code meets PEER_FLOOD on the first, and some vendors call that a ban. Sending a message to someone who has not saved your number is exactly the action the limit removes, which is why the first symptom is usually there.
How to remove a telegram spam block
There is no telegram account limited access unlock button. Telegram's FAQ says early removal on request is not possible, so the realistic telegram account limited fix is to find out what you have and then wait out the period. Here is how to remove telegram spam block status, as far as anyone outside Telegram can:
- Open a chat with @SpamBot from the restricted account and press Start. The reply says whether the account is limited and, often, until when.
- If the reply names a date, stop all first messages from that account until then. Replies to people who write in are still fine.
- If you are sure the limit is a mistake, say so through SpamBot. That is the appeal route the spam FAQ names.
- For a team, check every account the same way. A SpamBot check only answers for the account asking, so one clean reply proves nothing about the others.
- After it lifts, change whatever caused it. The same pattern brings a longer limit next time.
Telegram account limited for no reason is still worth an appeal when it really is a mistake. It does not shorten a limit that was earned.
How do you avoid a ban when you send at volume?
The flood wait telegram fix and the answer to how to avoid getting banned on Telegram turn out to be the same advice. Respect the timer you were given, stop sending first messages to people who did not ask, and do not treat a second account as a way around the first one's wait. A telegram flood limit tells you the pace was too fast. A spam limit tells you the messages were unwanted.
Only the first is a question of speed.
Flood wait telegram solution for scripts
Read X, sleep for X, and send that request again once. Then lower the rate that caused it, because a loop that keeps its old speed after a wait usually earns a longer wait next. Never retry inside the wait; Telegram counts those calls too. Keep the telegram rate limit you met per account and per method in your logs, so the next run starts slower. Reads count as well. Paging back through a chat's history to find active commenters and exporting a large chat from Telegram Desktop both make long runs of requests that count against the same kind of limit.
The heaviest flood waits tend to sit on actions that create or join things. Working through a long list of groups to join meets them early, and making channels and groups by the batch meets them alongside a separate hard cap of 500 chats per account, which no wait will lift. Bulk contact work is similar: importing numbers and removing contacts so they stay deleted are both counted methods.
What a multi-account panel does with these errors
Telegram Solutions is a Windows desktop panel that runs the accounts you bring. In the panel's source we reviewed, its mass DM module logs each FLOOD_WAIT with its seconds against the account and target, and it stops an account completely at its first PEER_FLOOD rather than moving to the next name, because a limited account cannot reach strangers anyway. Before a run, checking a batch of sessions shows which logins still work. Rich posts sent through PostBot codes from an account still count as that account's own messages.
What software cannot do matters more. There is no telegram unlimited account, and no tool lifts a flood limit, a 429 or a spam restriction, because all of them live on Telegram's servers. Pacing and an activity bot that keeps accounts in ordinary use change how an account behaves, not what the people receiving its messages think of them. Telegram's Terms of Service forbid using the service to send spam, and messages to people who never asked for them are what too many requests telegram eventually turns into: reports, and then a limit.