Small configuration errors, such as BGP leaks, VLAN misconfigurations, and route redistribution mistakes, have triggered some of the largest outages in modern networks.
Most major network outages do not begin with hardware failure or sophisticated attacks. They begin with a routine change window and a configuration that looked harmless at the time.
A single command can alter routing behavior, collapse segmentation boundaries, or send traffic down paths no one intended. The devices do exactly what they were told to do. The problem is what they were told.
The following examples show how small configuration mistakes have triggered large outages in real networks.
Mistake 1. A single BGP route leak
BGP leaks are one of the fastest ways to destabilize large portions of the internet.
In 2019, a small ISP accidentally advertised more than 70,000 routes learned from upstream providers. Those routes propagated globally within minutes and temporarily disrupted services, including Google and Cloudflare.
The root cause was simple. Prefix filtering and maximum prefix limits were not enforced on the session. Once the routes entered upstream networks, they spread across multiple autonomous systems almost immediately.
Mistake 2. Redistributing the wrong routing table
Route redistribution allows protocols such as OSPF, EIGRP, and BGP to exchange routes. It also introduces a serious risk when redistribution policies are not tightly scoped.
Outages occur when engineers redistribute the entire internal routing table instead of a filtered subset. Thousands of unexpected routes suddenly appear in adjacent routing domains.
The change itself may be one command. The resulting routing instability can trigger loops, convergence storms, and CPU spikes across multiple devices.
Mistake 3. VLAN trunk misconfiguration
Trunk ports determine which VLANs are allowed to traverse switch links.
A trunk configured to allow all VLANs can silently expand broadcast domains and collapse segmentation boundaries. Traffic begins appearing in parts of the network that were never intended to see it.
This is how management VLANs, storage networks, or voice segments occasionally leak into access layers where they have no business being.
Mistake 4. Spanning tree root changes
Spanning Tree Protocol still controls traffic flow across many enterprise Layer 2 networks.
Changing the bridge priority on the wrong switch can instantly move the root bridge. The entire Layer 2 topology recalculates, and traffic paths shift without warning.
In some networks, the new root bridge ends up being an access switch. Within minutes, it may be carrying traffic volumes it was never designed to handle.
Mistake 5. Overlapping IP subnets
Duplicate subnets can create some of the most confusing outages engineers encounter.
Everything appears correct when viewed individually. Routes look valid, and interfaces are configured properly. Yet packets disappear or arrive inconsistently depending on their origin.
The usual cause is simple. Someone reused an address range that already existed elsewhere in the network. ARP responses begin to compete, and traffic follows whichever device responds first.
Mistake 6. MTU mismatches across links
MTU mismatches rarely break connectivity completely. They break it just enough to be painful.
Small packets pass without issue while larger packets disappear somewhere along the path. Applications stall, file transfers fail, and troubleshooting quickly turns into guesswork.
The underlying problem is often a single interface or tunnel configured with an MTU smaller than the rest of the path.
Mistake 7. ACL rule ordering errors
Access control lists are evaluated from top to bottom.
A single rule inserted above an existing policy can completely change the outcome. Engineers sometimes add a temporary permit rule during testing only to discover later that it shadows a deny statement further down the list.
The configuration looks correct at a glance. The network obeys the first rule it encounters.
Mistake 8. NAT rule conflicts
NAT policies rarely remain clean for long.
Static mappings, dynamic pools, and policy NAT rules accumulate over time as new services are deployed. Eventually, the ruleset becomes complicated enough that translations behave differently depending on the source, destination, or protocol.
Engineers often discover these problems only when certain flows work perfectly while others fail with no obvious explanation.
Mistake 9. Disabling route filtering during troubleshooting
Many routing incidents begin during troubleshooting rather than normal operation.
An engineer temporarily disables prefix filtering or route limits to understand why a BGP session is not behaving as expected. The session stabilizes, the investigation moves on, and the protection is never restored.
Hours or days later, an unexpected advertisement spreads across the network, and no one remembers that the guardrail was removed during a change window.
When small commands have network-wide consequences
Networking protocols are designed to distribute information quickly. That strength also means mistakes propagate quickly.
Routing protocols advertise changes across large portions of the network within seconds. Switching protocols recalculates traffic paths immediately. A configuration mistake rarely stays local for long.
Experienced engineers know this and build guardrails accordingly. Prefix filtering, strict VLAN policies, configuration templates, and disciplined change control exist to limit the impact of human error.
Because in most outages, the network is not broken. It is doing exactly what someone configured it to do.
You may also like
- 11 times DNS mistakes were the real problem (and not the network)
- 6 cybersecurity myths that could derail your next network upgrade
- Think like a network automation engineer
About NetworkTigers
NetworkTigers is the leader in the secondary market for Grade A, seller-refurbished networking equipment. Founded in January 1996 as Andover Consulting Group, the company originally built and re-architected data centers for Fortune 500 firms. Today, NetworkTigers provides consulting and network equipment to global government agencies, Fortune 2000 companies, and healthcare companies. Visit www.networktigers.com
