Short answer. A Telegram flood wait is a timed rate limit. Telegram's API returns error 420 with FLOOD_WAIT_X, where X is the number of seconds to pause before repeating the same request; bots receive HTTP 429 with a retry_after value instead. The fix is to wait the stated time. PEER_FLOOD and a spam block belong to a different system: a moderation limit with no timer, which waiting and retrying does not clear.
Seven different messages are searched as one problem. A Telegram flood wait, a bot's 429, a slow-mode notice, a login code refusal, PEER_FLOOD and an "account limited" reply from @SpamBot all stop a send, and most pages ranking for flood wait telegram queries are client-library documentation that covers only the first of them.
The seven messages come from two systems with opposite repairs. A rate limiter tells the sender how many seconds to wait. A moderation limit tells the sender nothing, because people reported the messages and a wait was never the remedy.
Every Telegram figure below is quoted from Telegram's own documentation with the page named, as read on 10 October 2026. Where Telegram publishes nothing, this guide says so, which is the rule Sendhaus applies to all Telegram messaging work.
What is flood wait in Telegram?
The flood wait telegram meaning is narrow and Telegram defines it in one place. The API errors page describes error 420 FLOOD as too many attempts to call one method with the same inputs, and gives FLOOD_WAIT_X as the example, where X is a number of seconds. A Telegram flood wait is therefore scoped to a single method, and the server states its own duration inside the error.
"The maximum allowed number of attempts to invoke the given method with the given input parameters has been exceeded." Example: "FLOOD_WAIT_X: A wait of X seconds is required (where X is a number)".Telegram API, core.telegram.org/api/errors, 420 FLOOD
The same error travels under three spellings. It is searched as telegram floodwait, after the FloodWait exception classes in Pyrogram and Telethon, and as flood_wait telegram, after the raw FLOOD_WAIT_X string. Telegram flood control is the Bot API's wording for the same mechanism.
Telegram's own example of a flood is not about messages at all. The sentence that follows the definition reads: "For example, in an attempt to request a large number of text messages (SMS) for the same phone number." Sending is one of many actions the limiter covers.
FLOOD_WAIT_X. X is the wait in seconds.
retry_after in seconds.
Flood wait Telegram errors, sorted by the system that sent them
Five of the seven messages are rate limiters and two are moderation outcomes. A rate limiter names a wait or implies one, and the limit ends when the time passes. A moderation outcome follows spam reports, names no wait in the error, and is reviewed by people. Sorting the message into the right system comes before any repair, because the repairs are opposites.
| What you see | What produced it | Does waiting clear it? |
|---|---|---|
FLOOD_WAIT_X, error 420 | The API rate limiter, for one method and its inputs | Yes. X is the number of seconds |
429 with retry_after | The Bot API's flood control, for bots | Yes. retry_after is the number of seconds |
SLOWMODE_WAIT_X | A group's slow mode setting, in that one chat | Yes, and only that chat is affected |
FLOOD_PREMIUM_WAIT_X | The rate limiter, on an action Premium exempts | Yes. The docs add that Premium removes it |
PHONE_NUMBER_FLOOD | The login system, after repeated code requests | Yes, but no duration is published |
PEER_FLOOD | Not defined on Telegram's API errors page; client libraries tie it to a spam limit | No timer is given |
| "Account limited" from @SpamBot | Moderators, after users pressed Report spam | Only the limit's own period; no early release |
Slow mode is the row most often misread as a personal penalty. Telegram's description of that error is "Slowmode is enabled in this chat: wait %d seconds before sending another message to this chat", so the group's settings produced it and every member posting there meets the same interval.
A telegram rate limit and a spam limit also differ in what triggers them. The rate limiter counts requests. The moderation system counts complaints, a mechanism examined in the guide to whether a Telegram mass report bot works, and what Telegram treats as spam is decided by the people receiving the messages. One sender can hit both in the same hour.
How long is a Telegram flood wait time?
The telegram flood wait time is whatever number the error carries, in seconds, and Telegram publishes no table of durations by method or by account. A wait can be a few seconds or many hours. The only documented way to learn the duration is to read X in FLOOD_WAIT_X, or retry_after on a bot's 429 response.
Client libraries hide short waits and surface long ones, which is why two developers describe the same Telegram flood wait differently. Each library sleeps through any wait below its own threshold and raises an error above it. The thresholds below are library defaults taken from each project's documentation. None of them is a Telegram figure.
| Library | Setting | Waits it sleeps through by default |
|---|---|---|
| Telethon | flood_sleep_threshold | Up to 60 seconds |
| MadelineProto | Flood timeout setting | Under 30 seconds |
| Pyrogram | sleep_threshold | Up to 10 seconds |
Long waits are reported, though not documented. One developer write-up on Tencent Cloud's community site describes a bot that sent a burst of messages after a session switch and received a 429 with a retry_after of about 26,965 seconds, close to seven and a half hours. That is a single report from a third party, and it shows the range rather than a rule.
The flood wait Telegram fix, in the order that works
The flood wait telegram fix is to stop calling the method that returned the error, wait the full number of seconds, and repeat the request once. No documented action shortens the wait. The lasting flood wait telegram solution is a lower request rate, because a wait that returns every hour is reporting the sending pattern and not a fault in the account.
-
Read the number before doing anything
A
FLOOD_WAIT_Xor aretry_afterstates its duration. An error with no number in it is a different limit, and the sections onPEER_FLOODand spam blocks below apply instead. -
Wait the whole duration on that method
Telegram's definition ties the limit to "the given method with the given input parameters". Other actions on the account may keep working during a Telegram flood wait, and repeating the limited call early only returns the error again.
-
Leave the device alone
The server applied the wait. Reinstalling the app, logging out or switching networks changes nothing about a counter held on Telegram's side, and repeated logins can raise a separate login flood.
-
Find the loop that asked too often
A wait that recurs has a cause in code or in habit: a script calling one method in a tight loop, a tool retrying on failure, or a person forwarding to dozens of chats in a minute. The repair is a queue with a fixed pace and a single retry after the stated delay.
The workaround sold most often is to spread the same sends over more accounts. The rate limiter then sees less per account, while the reports that lead to a spam limit follow the messages to every account that sent them. The same arrangement is sold for filling groups, and the guide to what a Telegram member add bot can call covers that side.
What does Telegram 429 Too Many Requests mean for a bot?
Telegram 429 Too Many Requests is the Bot API's version of a flood wait. A bot went past one of the broadcast limits in the Bot FAQ, and the response carries a retry_after field stating how many seconds to pause. The telegram bot too many requests error is the only limit on this page for which Telegram publishes the thresholds that trigger it.
"In case of exceeding flood control, the number of seconds left to wait before the request can be repeated".Telegram Bot API, ResponseParameters, retry_after
| Scope | Telegram's wording | What kind of figure it is |
|---|---|---|
| One chat | "avoid sending more than one message per second" | Advice. "We may allow short bursts that go over this limit" |
| One group | "bots are not be able to send more than 20 messages per minute" | A stated cap |
| Bulk notifications | "not able to broadcast more than about 30 messages per second" | A cap, approximate by its own wording |
| Paid broadcasts | "up to 1000 messages per second" | Opt-in, at 0.1 Stars per message over the free 30 per second |
Those four rows are the whole published set of telegram rate limits. Paid broadcasts carry an entry condition in the same FAQ: "a bot must have at least 100,000 Stars on its balance and at least 100,000 monthly active users." Most bots never qualify, so the free tier is the working limit.
Logs usually show the response as a line such as "Too Many Requests: retry after 35", which is why the error is searched as telegram too many requests retry after. Wrappers and dashboards reword the same response, so it also appears as telegram too many requests try again and as too many requests telegram. All of them are one event: retry_after seconds must pass before that request is repeated.
The arithmetic follows from the bulk figure. At about 30 messages per second a bot needs roughly 2 hours 19 minutes to reach 250,000 subscribers and about 9 hours 16 minutes to reach one million, before any retry. The Bot FAQ's own advice is to spread a large send "over longer intervals (e.g. 8-12 hours)".
One million messages at the paid ceiling of 1,000 per second take under 17 minutes. With the first 30 per second free, about 970,000 of them are billable, which comes to roughly 97,000 Stars.Derived by Sendhaus from the Bot FAQ's published figures; illustrative, not a quote
A bot only reaches users who started it, so the list is opted-in by construction. That is the model behind queue-paced broadcast messaging, and the timing side is covered in the guide to what the Telegram scheduler accepts. Where the list comes from matters as much as the pace, which is the subject of what a Telegram scraper can and cannot collect.
Is there a Telegram message limit per day?
Telegram publishes no telegram message limit per day, for personal accounts or for bots. The published sending figures are per second and per minute, and all of them sit in the Bot FAQ. For personal accounts Telegram's documentation states no telegram send limit of any kind, so every daily number in circulation comes from a vendor, a help desk or a forum.
The phrase telegram message limit also covers length, and that figure is documented. The Bot API describes the text of a message as "1-4096 characters after entities parsing". A telegram message limit exceeded notice on a single long post is usually that cap, or the scheduled-message cap, which the API reports as "There are too many scheduled messages."
| Figure stated as fact | Who states it | In Telegram's docs? |
|---|---|---|
10–15 cold messages a day, 3–5 for a new account | A messaging-API vendor's blog | No |
15 new contacts a day by phone number | A help-desk product's guide | No |
20–50 messages a day to people with no prior chat | A support platform's guidelines | No |
About 200 username searches a day | The same help-desk guide | No |
None of the four can be tested, and they disagree with each other. A telegram send message limit quoted without the account age, the recipients and the complaint rate it applied to describes one vendor's experience. The telegram dm limit that matters to a personal account is set by reports, as the next two sections show.
The basics of how to DM someone on Telegram are unaffected by any of this, outside the case explained in why an account can only message mutual contacts: a message to a contact or a reply to an incoming chat meets no documented cap. The limits appear when the same account opens many new chats, which is the subject of what Telegram documents about mass DM.
Peer flood Telegram errors: why waiting does not clear them
A peer flood Telegram error is a different thing from a flood wait. PEER_FLOOD carries no number of seconds, and Telegram's API errors page does not define it. Telethon's documentation says that errors like PeerFloodError mean "you're limited", and points to @SpamBot to check. Waiting a fixed time and retrying is the wrong repair, because no timer was set.
A limited account behaves the way Telegram's Spam FAQ describes. That FAQ says: "Limited accounts can send messages to people who have their number saved as a contact. You can also always reply to anyone who messages you first." Existing conversations keep working and new ones to strangers fail, which is the behaviour behind the mutual contacts only message in the apps.
Across three core.telegram.org pages read on 10 October 2026, the API errors page and the error tables for messages.sendMessage and channels.inviteToChannel, the string PEER_FLOOD appears zero times.Sendhaus review of Telegram's API documentation, 10 October 2026
A telegram spam restriction of this kind is triggered by adding as well as by messaging. The Spam FAQ applies the same expectation to placing people in groups they did not ask for, which is how invite member bots run on personal accounts end up limited without sending a single direct message.
How to remove Telegram spam block restrictions
A telegram spam block is lifted by time or by a review requested through @SpamBot, and Telegram documents no third route. The Spam FAQ says a first case will "most likely" last "a few days or so", that repeat cases last longer, and that early release "is impossible". The honest answer to how to remove telegram spam block limits is short: confirm the limit, appeal only if it was applied in error, and wait.
-
Confirm the limit with @SpamBot
Open @SpamBot from Telegram's own search and start it. The bot states whether the account is limited. A telegram account restricted by moderators shows there, while a flood wait does not.
-
Use what still works
A limited account can still write to people who saved its number and can reply to anyone who writes first, per the Spam FAQ. Customers who start the chat themselves are unaffected.
-
Appeal only a wrongly applied limit
The FAQ's wording is "If you are sure that the limit was wrongfully applied to your account, please contact our @SpamBot." Telegram publishes neither the review criteria nor a response time.
-
Stop the sends that caused it
The same FAQ warns: "If you keep writing unwanted messages to strangers, you may lose the ability to do so forever." Continuing from the same account during a limit is the documented path to a permanent one.
Telegram account restricted for no reason: the documented causes
A telegram account restricted for no reason usually has one of three causes that Telegram itself describes: the phone number's history, the type of number, or reports from recipients who found ordinary messages unwelcome. Telegram's Spam FAQ concedes the first two in plain words and apologises for them, and it names @SpamBot as the place to explain the case.
"Some numbers may trigger an overly harsh response from our system, either due to their previous owners' activities or due to them being certain virtual/VOIP numbers. We're sorry if this resulted in your account being limited for no reason."Telegram Spam FAQ, telegram.org/faq_spam
The third cause surprises people more. The Spam FAQ says: "For private messages, it really doesn't matter what you send, as long as the receivers find it unwelcome." A polite greeting to twenty strangers can produce the same reports as an advertisement, so a telegram account limited for no reason often did nothing that looks like spam to its owner.
Telegram also allows for its own error. The same FAQ says that "even the best systems, algorithms and well-trained people can make mistakes sometimes", which is the stated purpose of the @SpamBot appeal.
What does a phone number flood Telegram error mean at login?
A phone number flood Telegram error means the login system refused to send another code. The error table for the method that requests a login code lists PHONE_NUMBER_FLOOD with the description "You asked for the code too many times." The error concerns sign-in attempts on one number and has no connection to how many messages the account sent.
The same table carries two neighbours that are easy to confuse with it. PHONE_PASSWORD_FLOOD reads "You have tried logging in too many times." PHONE_NUMBER_BANNED reads "The provided phone number is banned from telegram", and it is a ban, with no wait attached. Telegram publishes no duration for either flood; when the response is a FLOOD_WAIT_X, X is the duration.
Is there a Telegram unlimited account?
No Telegram unlimited account exists in any Telegram document. The phrase belongs to sellers of aged accounts and bulk tools. Telegram's FAQ uses the word unlimited for audiences, describing "channels for broadcasting to unlimited audiences" beside groups of "up to 200,000 people". The reach is unlimited for a channel that people chose to follow, and no account type is exempt from flood control.
Telegram Premium changes one flood error according to the documentation. The API errors page says of FLOOD_PREMIUM_WAIT_X that "the user may also purchase a Telegram Premium subscription to remove this limitation", and refers the reader to its file handling page. No Telegram page states that Premium shortens an ordinary Telegram flood wait or lifts a spam limit.
The only published way to raise a sending ceiling is the paid broadcast tier for bots, with its 100,000-user entry condition. A vendor offering a mass messaging platform with "no limits" is describing something Telegram's documentation does not contain, which is why Sendhaus works only from the rates Telegram publishes.
How to avoid getting banned on Telegram while sending at volume
How to avoid getting banned on Telegram comes down to who receives the messages, with pace a distant second. Telegram's Terms of Service bind every user not to "use our service to send spam or scam users", and the Spam FAQ sets the test: "Please only contact people if you're sure that they are expecting messages from you." A slow send to strangers still fails that test.
- Send to people who opted in: users who started a bot, or subscribers who joined a channel.
- Pace a bot under the Bot FAQ's figures and honour every
retry_afterin full. - Treat a recurring Telegram flood wait as a design fault in the queue.
- Reach strangers with paid placements. The published Telegram Ads price floor is low, and the guide to what a Telegram ads agency actually sells covers the managed route.
A layer of law sits above Telegram's rules. In the European Union, Article 13 of the ePrivacy Directive requires prior consent for unsolicited direct-marketing messages sent by electronic mail, and national rules elsewhere set their own conditions. This guide is not legal advice; the point is that a send Telegram would tolerate can still be unlawful.
What Telegram does not publish about flood limits
Telegram documents the form of a flood wait and almost none of its thresholds. No telegram flood limit table exists for user accounts, no schedule of spam-limit durations is published, and PEER_FLOOD has no official definition on the API errors page. Any page stating these numbers as fact is reporting its author's observations.
| Detail | Status in Telegram's docs |
|---|---|
Request counts that trigger FLOOD_WAIT_X, per method | Not published |
| A daily message cap for personal accounts | Not published |
The meaning and duration of PEER_FLOOD | Absent from the API errors page |
| How many reports lead to a spam limit | Not published |
| @SpamBot review criteria and response time | Not published |
| Any effect of Premium on spam limits | Not stated |
The grammY documentation reports that the exact bot limits are unspecified and that, according to Telegram, knowing them is "useless and harmful". That is a third party's account of Telegram's position, and it fits the gaps in the table above.
Frequently asked questions
What does FLOOD_WAIT_X mean in Telegram?
FLOOD_WAIT_X is the example Telegram's API documentation gives for error 420 FLOOD, described as "A wait of X seconds is required (where X is a number)". The same page defines the 420 error as the maximum allowed number of attempts to invoke the given method with the given input parameters being exceeded. X is a duration in seconds, set by the server for that one method.
How do I fix a Telegram flood wait?
Stop calling the method that returned the error, wait the full number of seconds in FLOOD_WAIT_X, then repeat the request once. Nothing done on the device shortens a wait the server applied. If the Telegram flood wait keeps coming back, the cause is the request rate, so the lasting repair is a queue that paces sends below the limit instead of a faster retry.
Why does my Telegram bot return 429 Too Many Requests?
The bot went past a broadcast limit in the Bot FAQ: more than one message per second in a single chat, more than 20 messages per minute in a group, or more than about 30 messages per second in bulk. The response carries retry_after, which the Bot API describes as the number of seconds left to wait before the request can be repeated.
Is PEER_FLOOD the same as a flood wait?
No. A flood wait states a number of seconds and ends when they pass. PEER_FLOOD states no duration, and it does not appear on Telegram's API errors page. Telethon's documentation says the error means the account is limited, which matches the spam limit in Telegram's Spam FAQ: a limited account can still message people who saved its number and reply to anyone who writes first.
How long does a Telegram spam block last?
Telegram's Spam FAQ gives no fixed schedule. For a first case it says "most likely your account will be limited for a few days or so", adds that "Repeated offences will result in longer periods of being blocked", and warns that continued unwanted messages to strangers can remove the ability to send them forever. Early release is ruled out in the same FAQ.
Does Telegram Premium remove flood limits?
Only one, according to the documentation. The API errors page says of FLOOD_PREMIUM_WAIT_X that the user may also purchase a Telegram Premium subscription to remove this limitation, and it points to the file handling page for that error. No Telegram page states that Premium shortens FLOOD_WAIT_X, clears PEER_FLOOD or lifts a spam limit.
Sources
- Telegram API, error handling — the 420 FLOOD definition,
FLOOD_WAIT_X,FLOOD_PREMIUM_WAIT_Xand the absence ofPEER_FLOOD. - Telegram Bot FAQ, broadcasting to users — the per-chat, per-group and bulk figures, 429 errors and the paid broadcast conditions.
- Telegram Bot API reference — the
retry_afterdescription,allow_paid_broadcastand the 1-4096 character text length. - Telegram Spam FAQ — what a limited account can still do, how long limits last, @SpamBot and the virtual-number passage.
- Telegram API, auth.sendCode —
PHONE_NUMBER_FLOOD,PHONE_PASSWORD_FLOODandPHONE_NUMBER_BANNED. - Telegram API, messages.sendMessage — the slow mode and scheduled-message errors.
- Telegram Terms of Service — the spam clause.
- grammY documentation, flood limits — the third-party quotations on ignoring rate limits and on unspecified limits.
- Directive 2002/58/EC, Article 13 — consent for unsolicited direct-marketing communications.
Seeing a Telegram flood wait in a live send?
Send the error text and the send pattern that produced it. You get a written read on which limit it is, whether waiting clears it, and what the queue has to change so the error stops returning.