Back to All Scenarios
PASSEDnetwork / isp_circuit_brownout
ISP Circuit Brownout — Intermittent Packet Loss
The primary ISP circuit is experiencing intermittent packet loss (5-15%) due to a degraded fiber segment. Not a full outage — the circuit stays up but quality degrades. VoIP calls have choppy audio, video conferences freeze, and cloud app performance is poor. ISP ticket opened but ETA unknown.
Pattern
UNKNOWN
Severity
CRITICAL
Confidence
95%
Remediation
Remote Hands
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | UNKNOWN | UNKNOWN | |
| Severity Assessment | CRITICAL | CRITICAL | |
| Incident Correlation | Yes | 26 linked | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Remote Hands — Corax contacts on-site support via call, email, or API |
Scenario Conditions
1Gbps ISP fiber circuit. Packet loss: 5-15% intermittent. Latency spikes: 150ms (baseline: 8ms). Jitter: 45ms. Circuit stays UP (no failover trigger). 200 users. VoIP, Teams video, and SaaS apps affected.
Injected Error Messages (2)
ISP circuit brownout detected — WAN interface Gi0/0 packet loss 5-15% intermittent, latency surges to 150ms (baseline 8ms), ifInErrors incrementing, circuit UP but quality impaired, ISP ticket #INC4872910 opened, no ETA for fiber repair
Real-time communication severely impacted — audio quality score 1.8 (minimum acceptable: 3.5), R-factor: 52, packet loss causing audio dropouts, buffer overflow on voice streams, Teams/Zoom video freezing every 10-15 seconds, users reporting unusable call and video quality
Neural Engine Root Cause Analysis
The incident is caused by physical fiber optic infrastructure degradation on the ISP's network, resulting in a circuit brownout condition. The WAN interface Gi0/0 is experiencing 5-15% intermittent packet loss and latency spikes from 8ms baseline to 150ms, with incrementing ifInErrors indicating physical layer problems. This is a carrier-side infrastructure issue that requires ISP intervention to repair the damaged fiber segment, as evidenced by the opened ISP ticket #INC4872910.
Remediation Plan
1. Monitor ISP ticket #INC4872910 progress and request regular updates with ETA. 2. Implement traffic load balancing to secondary WAN circuits if available to mitigate impact. 3. Adjust QoS policies to prioritize critical traffic during degraded performance. 4. Set up enhanced monitoring on backup circuits to ensure redundancy readiness. 5. Consider implementing WAN optimization techniques to reduce packet overhead during the brownout period. 6. Escalate with ISP if no progress updates are provided within 2 hours given critical severity.
Tested: 2026-03-30Monitors: 2 | Incidents: 2Test ID: cmncjo2ys033uobqe69c5feeg