Oct 30, 2026 · 4 min read
Telegram lets a bot post 20 messages a minute in a group, so 50 alerts can take about 2.5 minutes to arrive. How to test any hub, the limits it works around and the controls that matter.
TradingWizard AI5 min read
To compare crypto alert hubs, fire the same burst of alerts through each one and time the last message that arrives, then check whether the hub merged, queued or dropped the rest. Chat apps cap how fast a bot can post: Telegram allows a bot 20 messages a minute in a group, so 50 alerts that fire together take about two and a half minutes to reach you unless the hub merges them into one message.
A hub can only deliver as fast as the channel lets it. These limits come from each platform's own documentation.
| Channel | Published limit | What it means during a fast move |
|---|---|---|
| Telegram group | 20 bot messages per minute | One message every 3 seconds at best |
| Telegram private chat | About 1 message per second | 50 alerts take about 49 seconds |
| Telegram, many users at once | About 30 messages per second | A large alert list goes out in waves |
| Discord | 50 requests per second per bot, plus per-route limits | Over the limit, Discord answers "try again later" with a wait time |
| TradingView alert | Stopped after more than 15 triggers in 3 minutes | An alert that fires more often than every 12 seconds switches itself off |
| TradingView webhook | Cancelled if the receiving server takes over 3 seconds | A slow hub can miss the alert before it starts delivering |
Sources: Telegram Bot API FAQ, Discord developer docs on rate limits, TradingView support pages on alert limits and webhooks.
Hypothetical example. BTC drops fast and 50 of your coin alerts trigger in the same second. Your hub sends each one as its own Telegram message to a group.
The last alert still says "BTC crossed $60,000". By the time you read it, price is near $59,410.
Now the same burst through a hub that merges alerts. It sends one message listing all 50 coins. A Telegram message can hold up to 4,096 characters, so 50 lines of about 40 characters fit in one post. You get everything in about a second.
If the hub does neither and simply ignores Telegram's "try again later" reply, some of those 50 alerts never arrive at all. That is the worst case, because nothing tells you they are missing.
Run the same test on each hub you are comparing and put the slowest delivery time side by side. That number tells you more than the list of supported channels.
An alert tells you a level broke. A TradingWizard bot also shows what it read, why it traded or waited, and when it checks next. Demo trades use simulated money. No real orders are sent. Set up a demo bot on BTC in Wiz and put its last decision next to your alert log.
Which crypto alert hub tracks last triggered timestamps reliably covers the trigger time in more detail. A TradingView alert that fires more than 15 times in 3 minutes is stopped, so a level that price keeps crossing needs a cooldown or a wider trigger before the next fast move.
Oct 30, 2026 · 4 min read
Jun 24, 2026 · 8 min read
Jun 23, 2026 · 8 min read
Jun 8, 2026 · 5 min read