Skip to content
Signalcrest
Back to feed
hackernewsbusiness

Telstra outage: The night a network decided the year was 2006

Major Telstra outage shows need for network redundancy planning.

Steady
Signal score
17
as of 1d ago
Trajectory
Cooling
7-day est. ~1

Why this scored 17

every term, weighted
Velocity+0.0 / 40

Engagement gained per hour since the last capture, against the fastest item on its own source

Acceleration+11.3 / 25

Whether that velocity is itself speeding up, as a per-hour rate

Cross-source spread+0.0 / 25

How many independent communities are talking about the same entity

Recency+7.9 / 10

Decays to zero over 14 days

Saturation penalty2.6 / 30

Subtracted once something is big and old — we rank what's next, not what's peaked

Composite16.6

Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On a topic'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 guarantee

7-day

~1

range 013

14-day

~0

range 014

30-day

~0

range 019

Signal history

7-day window (free)
121

projected trajectory (estimate, not a guarantee)

Entities

telstra
Embed a live signal badge
Signalcrest signal badge
[![Signalcrest signal](https://www.signalcrest.app/api/badge/hn%3A49748957)](https://www.signalcrest.app/topic/hn%3A49748957)

Drop this in a README or blog post — it updates automatically as the score moves.