yandex
for security engineers, devops
Why this scored 13
every term, weightedIts fastest-moving item, measured against the pace of its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities its own items come from
Decays to zero over 14 days, counted from when we first saw it
Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it
Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On an entity's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology
Outlook
low confidence · estimate, not a guarantee7-day
~20
range 0–32
14-day
~20
range 0–34
30-day
~19
range 0–39
Signal history
7-day window (free)projected trajectory (estimate, not a guarantee)
The evidence
The live items this entity's score aggregates — every community independently talking about it right now. This is the corroboration, shown, not claimed.
- 118
Bot traffic from Yandex
Yandex bot traffic may affect site performance and analytics. · for security engineers, devops
hackernewsSteadysecurity1d ago - 216
Yandex Takes a Second Data Center Hit in 48 Hours
Yandex experienced another data center outage within 48 hours, highlighting reliability risks. · for site reliability engineers
hackernewsSteadybusiness3d ago - 315
Yandex bot traffic down 99% after data center attack
Yandex bot traffic fell 99% after a data center attack, impacting site indexing. · for site reliability engineers, security engineers
hackernewsSteadysecurity11h ago