Your own alerts, by email. A price, a coin, a topic, a hack over an amount or your coin stuck somewhere: we check every ten minutes and email only you.
This week i
127 alerts in the last 7 days, most of them in market moves (66).
Market moves
66 in 7 days
Latest: ONDO ▲ +5.8% · 1h ago
Open
Security & incidents
43 in 7 days
Latest: Quicknode 1h 38m · ongoing
Open
Informational
18 in 7 days
Latest: NYSE puts Avalanche at the center of its tokenized stock… · 1h ago
Open
What matters most i
The four rules, their thresholds and why those and not others
| Rule | Watches | Fires when | Why that number |
|---|---|---|---|
| A service the market runs on is in trouble | service_status_change | a watched service moves into down or degraded | No threshold to choose: the source reports a closed state. The care is elsewhere — only changes with a recent observation count, so a service nobody checked lately is «unknown», not «broken». Without that, 241 of 300 services would have fired on the first day. |
| A theft larger than most on record | security_incident | a theft above the 90th percentile of every theft we have with a figure | Of 2,845 recorded thefts with a figure the median is $700K and the 90th percentile $20M. A percentile rather than a round number, so the bar moves with the archive instead of ageing. |
| It moved and nothing explains it | price_move, move_finding | a move of a single asset with no cause found, on a day the whole market held | No percentage threshold here: price_move is already the filtered set. What this adds is the absence of a cause, which is the one thing an aggregator cannot tell you. |
| Five newsrooms inside two hours | story, item, item_discovery | 5 distinct newsrooms within 120 minutes | Gathering five newsrooms takes 8.9 hours at the median and 30 at the 90th percentile, so two hours is four times faster than usual. It fired 11 times in seven days: 1.6 a day. At four newsrooms it would be 6.6 a day and at three, 23 — that is not an alert, that is the river. |