telstra
for SREs, network engineers
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
Signal history
7-day window (free)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.
- 122
Telstra outage explained: how one GPS card set the network to 2006
A faulty GPS card forced Telstra's network rollback, underscoring the need for resilient config management. · for SREs, network engineers
devtoSteadydevtools1h ago - 217
Telstra outage: The night a network decided the year was 2006
Telstra experienced a network outage, highlighting risks for services relying on its infrastructure. · for network engineers, ops teams
lobstersSteadybusiness15d ago - 317
Telstra outage: The night a network decided the year was 2006
Major Telstra outage shows need for network redundancy planning. · for network ops
hackernewsSteadybusiness12d ago