> For the complete documentation index, see [llms.txt](https://docs.raybot.app/start/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raybot.app/start/help-and-support/raybot-and-telegram-rate-limits.md).

# RayBot and Telegram Rate Limits

If you've landed on this page, chances are you've already hit a rate limit.

### 😶‍🌫️ What's happening

Telegram limits how many messages a bot can send. Go over the limit and Telegram blocks the bot from sending — anywhere from a few minutes to a full day.

{% hint style="info" %}
**The bot isn't crashing or broken.** It's running fine — Telegram just isn't letting its messages through to you.
{% endhint %}

| Where              | Limit                    |
| ------------------ | ------------------------ |
| Per user           | 1 message per second     |
| In a group         | \~20 messages per minute |
| In direct messages | \~40 messages per minute |

> **⚠️ These aren't hard cut-offs. Occasional bursts of \~40 messages per minute are fine — what gets you limited is a sustained firehose at that rate.**

***

### 🔍 How to tell

**You're rate limited if you see any of these:**

* 🛑 A warning in your chat: `You are receiving too many notifications`
* ⏳ A note at the bottom of an alert: `Too many messages - delayed due to Telegram rate limits`
* 🔇 Notifications stop arriving altogether

**To confirm:** connect [**@ray\_status\_bot**](https://t.me/ray_status_bot) — it alerts you when one of your bots gets limited, and `/limits` shows the status of all of them.

***

### 1️⃣ Get your notifications back

Send `/bots` → pick a bot → open it → send `/switch` → select the limited bot.

All your wallets, settings and filters transfer over automatically.

{% hint style="info" icon="align-justify" %}
**Using groups?** Move to [**Dedicated Bots**](/start/telegram/interface-navigation/dedicated-bot.md) — they get limited far less often than a shared RayBot in a group.
{% endhint %}

***

### 2️⃣ Cut down the volume

This is the real fix. Everything else just spreads the load around.

#### ⚙️ Clean up your filters

Clears out the on-chain service events most people don't need if you're tracking traders' buys and sells.\
Path: `/start` → **Settings** → chain.

| Network                       | Turn off                                                                                                                |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| **Solana**                    | Migrate · DRiP · cNFT · Burn · Unknown · Add / Remove Liquidity · Claim Fee / Receive Fee / Update Fee · Claim Cashback |
| **Solana** → Advanced Filters | Low liquidity transfers · Likely Scam Transfers · StreamFlow · Freeze                                                   |
| **EVM**                       | Add Liquidity · Remove Liquidity · Approvals · Tips Maestro · Spoofed transfers                                         |

Then set your minimum thresholds (same idea on EVM):

| Filter                 | Value |
| ---------------------- | ----- |
| Min Trade SOL          | 0.1   |
| Min SOL Transfer       | 0.1   |
| Min Token Transfer USD | $5    |
| Min Other USD          | $5    |

{% hint style="info" %}
💡 These filters cut out up to 95% of the spam and scam activity that lands on tracked wallets. You'll still receive all the core transactions and interactions with known protocols.
{% endhint %}

#### 🔀 Spread the load

Don't keep 1,000 wallets in one bot.

| Approach                                                                                             | How                                                                          |
| ---------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
| **Split across bots**                                                                                | FOMO wallets apart from regular ones · EVM apart from SOL · or by importance |
| [**Backup bot**](/start/help-and-support/raybot-and-telegram-rate-limits/setting-up-a-backup-bot.md) | `/backup` in DMs — takes over if your main bot gets limited                  |
| **2+ bots in one group**                                                                             | If the first is limited, the second keeps sending                            |

{% hint style="info" %}
The multiple-bots trick works in \~80% of cases. Telegram sometimes limits **the whole group** rather than one bot — then every bot inside is affected at once.
{% endhint %}

***

#### 🆘 Safe Mode to Prevent Group Rate Limits

Telegram recently added new “spam” filters that can rate-limit bots sending messages with many external links in groups.

To help prevent this, we’ve introduced **Safe Mode**. If your group was recently rate-limited by Telegram, Safe Mode will automatically turn on:

* 🚫 Disables all external links
* 🔹 Removes the # sign before tickers
* ✅ Keeps buttons intact

You can also toggle Safe Mode manually in your groups at any time:

* `/safe_on` – turn it on
* `/safe_off` – turn it off

***

Still hitting limits after all this? Message [**@ray\_help\_bot**](https://t.me/ray_help_bot) and we'll go through your setup with you.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.raybot.app/start/help-and-support/raybot-and-telegram-rate-limits.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.