Use casesIt’s up, but it’s bad
A circuit keeps flapping. Contain it, then make the carrier fix it properly.
A marginal circuit that bounces four to eight times an hour is worse than one clean outage. Contain it so traffic stops thrashing, then collect the evidence while it is still happening.
Recognize it
You’re here if
- Availability toggles several times an hour, for short intervals.
- Path-change counts on the tunnel are far above normal.
- Alert volume for one site is climbing and users report resets.
Do this
5 steps, in order
Confirm the pattern
Pick the site and the Availability metric. Use the widest window.
Open Explorer- Look for
- Repeated short dips, several per day or per hour, with latency otherwise normal.
- What it means
- Normal latency between dips rules out the middle mile. This is the last mile or the media.
Contain it
Review the recommendation to dampen the path or pin the tunnel to the stable backup.
Open Remediation- Look for
- A reversible action with a rollback plan.
- What it means
- Keep the circuit out of rotation until its errors clear. A stable failover beats a flapping primary.
Count it for the contract
Open SLOs and find the link. Read actual availability against target and the error budget used.
Open SLOs- Look for
- Actual availability below the contractual floor.
- What it means
- This is the number for the credit claim.
Quiet the noise
Check that the cooldown and chronic policies are folding this flap into one alert instead of paging every bounce.
Open Noise Agent- Look for
- The flap collapsed to one situation with a recurrence count.
- What it means
- One page with a count beats forty pages.
Push for a permanent repair
Use the incident’s evidence on the carrier ticket. Ask for media replacement or connector reseat, not another temporary fix.
Open Governed Brain- Look for
- Dated failover events and an availability rollup.
- What it means
- Reweight this circuit as primary until it has been stable for a defined period.
Then decide
What you found decides what you do
IfDampening stops the storm
ThenKeep the circuit parked and chase the repair.
IfMonth-to-date availability is below the contract floor
ThenFile the credit claim with the dated evidence. Claim an SLA credit →
Watch out
Where this goes wrong
- A flapping circuit can hide a second fault in the noise it creates. Re-check the site once the flapping is contained.
The circuit is contained, the contract number is written down, and a repair is requested with evidence.
Keep going
Often next
Claim an SLA credit
Find the breaches, assemble dated evidence, and build the scorecard for the renewal.
~20 minFinance and vendor management, Network lead, Service ownerToo much noiseToo many alerts
Measure the noise, preview each suppression policy, then enforce deliberately.
~20 minNOC engineer, Network leadSomething is downA circuit went down
Confirm traffic actually moved, size the damage on backup, and set the failback condition.
~10 minNOC engineer, Network lead