---
title: "Telegram limits and restrictions"
locale: en
url: https://tlg.builera.app/en/docs/safety/telegram-limits
verified: 2026-10-24
app_version: "2.0"
---

# Telegram limits and restrictions

Distinguish Telegram's wait requirements from app quotas and learn how to handle restricted accounts.


Telegram may require you to wait, restrict contact, or freeze an account. These decisions are independent of the quotas you set in Telegram-Auto. Both **Free** and **Safe** must respect them.

## Distinguish the types of limits

| Signal | Meaning and app response |
|---|---|
| `FLOOD_WAIT` | Telegram requires a wait before continuing the relevant type of action. The app defers it and puts the account in a throttled state. |
| `SLOWMODE` | The group requires a gap between messages. This is a per-chat limit; it does not automatically make the account restricted. |
| `PEER_FLOOD` | A signal that outreach is restricted. The app marks the account as restricted and does not keep retrying as if this were a network error. |
| `spambot_limited` | A check indicates that the account is restricted. A wait and suitable evidence are required before recovery. |
| `frozen` | The account is frozen. The app stops actions that are not allowed and waits for a person to resolve it. |
| `banned` | The account is banned. The normal recovery button does not return this state to normal. |
| Revoked session | Separate from quotas: the account changes to **Needs to sign in again**. |

Privacy errors, a recipient blocking you, or a group not allowing messages do not automatically prove that the whole account is restricted.

## Telegram's required wait and the app's precautionary periods

No daily sending number guarantees that Telegram will accept every account. Telegram's actual response determines the wait required at the time of an action.

The safety code currently adds these precautionary periods:

- Deferral for `FLOOD_WAIT` is at least **2 times** the number of seconds Telegram requires.
- The throttled state lasts at least **24 hours**.
- The restricted state requires at least **72 hours** before a user can recover the account, subject to conditions.

These are app policies, not claims that Telegram always uses these periods. Repeated signals may push the wait further out. A timer ending does not mean the account is automatically recovered.

## Check with @SpamBot

The app provides an action to check restrictions through @SpamBot. A clean result is evidence for a recovery confirmed by a person, not a command to automatically reactivate the account.

For restricted accounts, the recovery code requires a suitable clean result after the waiting period. For frozen accounts, confirmation that the appeal has been handled is required. The app does not carry out the process for you and does not guarantee Telegram's approval.

> [!IMPORTANT]
> Do not repeatedly click recovery or switch to Free to skip the wait. The quota mode does not change Telegram's decision.

## What you should do

1. Open the account in **Accounts**.
2. Read its status, reason, and wait-until time.
3. Stop campaigns that are producing inappropriate behavior.
4. Resolve Telegram's requirements as the account's rightful owner.
5. Recover the account only when the displayed conditions are met.
6. Monitor the next task instead of immediately increasing activity.

Do not change proxies or move machines just to retry an action Telegram has blocked. Infrastructure changes do not remove restrictions and make investigation harder.

## Related

- [Handle FLOOD_WAIT](https://tlg.builera.app/en/docs/troubleshooting/flood-wait)
- [The two quota modes](https://tlg.builera.app/en/docs/concepts/free-and-safe)
- [Safety states](https://tlg.builera.app/en/docs/concepts/safety-states)
- [REST: check @SpamBot](https://tlg.builera.app/en/docs/reference/rest/accounts.check_spambot), MCP `accounts_check_spambot`