Airgram Docs

Useful

Spam block and FloodWait

Why Telegram restricts accounts and how to work so it happens less often.

Types of restrictions#

  • Spam block — a block on messaging people who haven't messaged you. It can be temporary (lifted on its own when the term ends) or permanent. Invites and broadcasts don't work with a spam block; in groups the account is already in, it can usually still write.
  • FloodWait — Telegram's reply: “too often, wait N seconds”. If the wait is under the limit from Settings, the account waits and continues; if it's longer, the account finishes its work in the task. Frequent FloodWaits are a reason to increase the pauses.
  • PEER_FLOOD — a type of spam block for contacting strangers in bulk. A typical response to inviting too fast.
  • Freeze — a restriction on the whole account. Telegram support lifts it on request; the program doesn't submit such requests.
  • Ban — the account can't be recovered.

How risky each module is#

  • High risk — invites, DM broadcasts, joining groups, number checking. These mean contacting strangers, which is exactly what gets you a spam block.
  • Medium risk — group broadcasts, creating channels, changing profiles in bulk.
  • Low risk — scraping, group search, reactions and views, auto-replies.

How to reduce the risk#

  • One proxy per account.
  • Warm-up: a filled-in profile, a few subscriptions, a couple of days with no workload.
  • Small limits per account and pauses of tens of seconds, with random variation.
  • Different message texts.
  • One account, one task at a time.
  • Account check before a big run.
  • Work only with an audience that's interested: reports weigh more than any pauses.

If mass spam blocks start#

  1. Stop the task: with the same settings, you'll lose the rest of your accounts.
  2. Lower the limits per account and increase the pauses.
  3. Reduce the number of threads.
  4. Check whether all the accounts are behind one proxy gateway.
  5. Check whether the accounts are warmed up.

A temporary spam block lifts on its own: let the account rest and don't put it back to work right away. You can try to appeal a permanent one: Remove Restrictions.

No settings can give a guarantee. In mass tasks, some accounts always end up restricted, so keep spare accounts and don't use valuable ones for broadcasts.