2 hour downtime due to "inadvertent change" during maintenance
Human error was cited as the reason Cisco.com was down for two hours yesterday. Cisco says it lost no business during the downtime and had not heard of any customers being adversely affected by it financially.
Still, how could the preeminent Internet company allow this to happen? How could they not plan for an eventuality like this?
Messages on NANOG and puck.nether.net mailing lists were abuzz that BGP tables worldwide dropped the route that led to Cisco.com — 198.133.219.0/24. But Cisco would not confirm that.
A company spokesperson issued this statement:
I can confirm that www.cisco.com experienced an outage of just over 2 hours this morning/afternoon. This was an inadvertent result of a change made during regular maintenance – a change that has since been reversed returning www.cisco.com to normal service. We thank our customers and partners for their patience and apologize for any inconvenience they may have experienced.
You would think, however, that safeguarding against a botched reconfiguration would be the first item on the zero downtime checklist. You would think.
More from Cisco Subnet:Win great stuff from Cisco SubnetCisco Alert newsletter. Like RSS readers? Subscribe to the Cisco Subnet RSS feedFollow Cisco Subnet on Twitter.
- BGP vulnerabilities in Cisco IOS
- Cisco WAAS rival Riverbed looking to buy?
- Can Cisco benefit from Avaya/Nortel deal?
- New features can open up Cisco IOS to hackers
- Employee reviews on Glassdoor.com slam Cisco
- Detente in Cisco/IBM “war”?
- One Cool ISO: Fully Automated Nagios
- Video rental records more private than cloud data
Like e-mail? Subscribe to the
