Score routing health from convergence, table utilisation, flap rate, session state and path redundancy.
Each dimension is scaled so that a healthy network scores near 100, then combined with weights that reflect what actually causes outages — convergence and stability carry the most, table headroom the least because it degrades gradually rather than suddenly. A single trend line is what gets routing health onto a management dashboard, and surfacing the weakest dimension keeps the score actionable instead of decorative.
Routing Health Score
Score = 25% convergence + 20% stability + 20% session health + 20% path redundancy + 15% table headroom, each dimension normalised to 0–100.
Capacity scoring
Table headroom score = 100 − 2.5 × (utilisation − 60), so it only penalises above 60%.
Score = 25% convergence + 20% stability + 20% session health + 20% path redundancy + 15% table headroom, each dimension normalised to 0–100. Each dimension is scaled so that a healthy network scores near 100, then combined with weights that reflect what actually causes outages — convergence and stability carry the most, table headroom the least because it degrades gradually rather than suddenly.
A single trend line is what gets routing health onto a management dashboard, and surfacing the weakest dimension keeps the score actionable instead of decorative.
This calculator takes 7 inputs: Measured convergence time, Convergence target, Route table utilisation, Route flaps per hour, Routing sessions down, Total routing sessions, Prefixes with a backup path. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
No — it is a defensible default, not a standard. Reweight it for your environment: raise path redundancy if you carry real-time media, raise table headroom if you are close to a FIB limit, and keep the weights fixed afterwards so the trend stays comparable.