Why many crypto alerts are hard to manage: a year of alerts on 20 coins

Many crypto alerts are hard to manage because most of them report the same event. We put a 2% hourly move alert on 20 large coins for a year: 5,611 alerts fired, and 58.5% of them arrived in just 304 hours when five or more coins moved together, almost always in the same direction.

Only one alert in five came alone, from the one coin that moved that hour. Those are often the alerts worth a closer look, and they are the easiest to lose in a pile of 20.

A year of alerts on 20 coins

Each alert below is an hour in which a coin closed at least the given percentage above or below where the hour opened. Same 20 coins, same year, three thresholds.

The average hides how uneven the days are. At 2%, the median day had 9 alerts, 32 days had none, and the busiest day, 5 June 2026, had 115.

A higher threshold cuts the count, but the pile-ups stay. Even at 3%, about half of all alerts came in hours when at least five coins fired together.

One hour, 20 alerts, one piece of news

On 21 January 2026 at 16:00 UTC, all 20 coins fell 2% or more within the same hour. Bitcoin fell 3.0%, Dogecoin and Sui fell 4.5%. A trader with this alert list got 20 notifications that all said the same thing: the whole market dropped.

That hour was not unusual. In 300 of the 304 hours when five or more coins fired at 2%, every coin that fired moved the same way. On 25 June 2026 at 13:00 UTC, Bitcoin fell 4.8% in an hour and all 20 coins hit even the 3% alert.

The most volatile coins take over the list

One percentage for every coin does not give every coin the same voice. At 2%, NEAR fired 627 times, OP 491, ARB 472 and UNI 461. Ethereum fired 159 times and Bitcoin 57. NEAR alone sent 11 alerts for every Bitcoin alert.

If the list mixes large and small coins, the small ones fill the screen. Setting each coin's threshold from its own usual hourly range keeps one noisy coin from burying the rest.

Does one Bitcoin alert cover the market?

Partly. In 197 of the 304 pile-up hours, Bitcoin itself moved 1% or more in that hour. But a 1% Bitcoin alert fired 383 times over the year, and it stayed quiet in 107 of the 304 pile-ups. It is a useful flag that the whole market is moving. It does not replace the coin alerts.

Five ways to cut the noise

1. Group alerts that fire in the same hour into one message. At 2%, that turns 5,611 notifications into 1,905.
2. Add a market flag. When a Bitcoin alert fires in the same hour as your coin alerts, read the group as one market move.
3. Read the alerts that came alone first. At 2% there were 1,126 of them, and each one was a coin moving without the rest.
4. Set thresholds per coin from its normal hourly move, so NEAR and Bitcoin speak at the same volume.
5. Delete alerts tied to a plan you no longer have. An old alert still fires.

For alerts that run while you sleep, read how to build a crypto alert setup for 24/7 monitoring.

Watching a bot next to your alerts

In TradingWizard you pick a market and an asset, set up a trading bot, and watch what it does. Each bot shows what it read, why it traded or waited, and when it checks next. Demo trades use simulated money. No real orders are sent.

Put demo bots on two coins from your alert list in /wiz and compare what each one read in the same hour.

How we counted

Coinbase hourly candles from the public API for BTC, ETH, SOL, XRP, DOGE, ADA, AVAX, LINK, DOT, LTC, BCH, UNI, AAVE, NEAR, ATOM, XLM, SHIB, ARB, OP and SUI, from 30 October 2025 to 29 October 2026, UTC. We kept the 8,665 hours in which all 20 coins had a candle (OP was missing 90). An alert is an hour whose close is at least the threshold above or below its open. Real price alerts also fire on moves inside the hour, so a live alert list would fire more often than these counts. This is a list of 20 large coins, not the whole market, and none of this is investment advice.