1. Incident Summary
Earlier today, around 17:30, our network monitoring detected a significant decline in traffic and elevated latency affecting services originating from our NZS location.

2. Root Cause Analysis
Following immediate investigation, our team has clearly identified the configuration errors responsible for the congestion:

Split-Horizon Misconfiguration: The newly deployed router was missing the required Split-Horizon configuration. This allowed routes learned via the new path to be re-advertised back onto the same ring, creating a suboptimal routing loop.

OSPF Metric Issue: The Open Shortest Path First (OSPF) cost was also incorrectly configured. This low metric amplified the Split-Horizon issue, causing the new, suboptimal path to be immediately advertised as the preferred path by the routing protocol.

These combined errors resulted in traffic converging onto the new connection, causing rapid saturation and the subsequent high latency observed by users.

3. Resolution Steps
Our Network Operations Team took immediate action to mitigate the issue and restore full stability:

The faulty routing source was identified and isolated.

The new router was promptly removed from our ring switches network.

Traffic immediately rerouted back to the stable, existing paths.

Full service stability and normal performance have been restored to the NZS location.

4. Next Steps & Assurance
The device remains isolated while its configuration is thoroughly reviewed and corrected to include the necessary Split-Horizon and OSPF settings.

We are currently closely monitoring the network to guarantee sustained optimal performance and prevent any recurrence.

We sincerely apologize for the inconvenience and service interruption this incident may have caused.