Well, not the whole Internet, but Con Edison (AS27506) “stole” several important prefixes on the Internet earlier today, probably by mistake. Earlier this afternoon, I saw a message on the NANOG mailing list claiming that Con Ed was “stealing” routes to Panix, the venerable New York ISP, who had previously been hit with another outage beyond their control. Looking quickly into this with Renesys Routing Intelligence, it’s far worse than that.
Con Edison apparently spent the better part of last night and today pretending to be a fair number of other people’s networks ranging from Martha Stewart Living to NYFIX, from The New York Daily News to Walrus Internet. This is bad. While some of these networks were customers of Con Edison, many were not. Did anyone else notice or care that all of their traffic was being misrouted or is Panix the only one of these people who isn’t asleep at the switch? Read on for significantly more detail about what we saw happen and who was affected.
[This is thrown together fairly quickly, so please expect corrections and addtions. Any questions that aren’t answered here can be posted in the comments and I’ll do my best to look at them and post replies.]
So, what happened? At 05:05:33 UTC 22 Jan 2006 Con Edison begins to announce a number prefixes (networks) owned by their customers. Announcing routes is the way that an Autonomous System introduces Internet addresses into the global routing table. It’s what allows the rest of us to send packets to the IP addresses contained within those networks. The normal way that service providers route traffic to their larger customers is that they wait for those customers to announce networks and then they just repeat the announcement. In this case, Con Edison started pretending to be their own customers. It’s probably not service-impacting, assuming they still know how to get the traffic to the customers, but it is odd.
They spew out huge numbers of announcements for the next several minutes. One of the first customers we see them announcing is Martha Stuart Living Omnimedia. It’s worth noting that this event is three and a half hours earlier than the problem that Panix complained about. So something strange was already at work at Con Edison.
Con Edison is lying (or making a mistake, but it’s definitely not true), but who is believing them? Some people call events like this network identity theft and although there’s no crime, the metaphor is somewhat apt. Just as in the case of real identity theft, it starts by someone pretending to be you, to own all of your networks. But what good is it if someone doesn’t believe them and spreads the lie? In this case, it’s UUnet (AS701). They keep believing the first set of lies until 05:22:29 UTC when the networks start moving back to their rightful owners.
But we’re not done! At 8:23:12 UTC Verio (aka NTT America, AS2914) starts believing some of the same lies that UUnet was already believing and Con Edison starts telling more lies. 8:31:15 UTC is the first instance of Con Edison announcing Panix’s route, and that one only ever appears through Verio. And here’s the worst part: as of about 4:00 UTC some of these networks are still being hijacked by Con Edison, for example, the more specific prefixes of Advanced Digital Internet listed below.
Here is a list of what appear to be honest-to-gosh hijackings of networks not belonging to or associated with Con Edison in any obvious way. I would assume that these would produce outages for the real owners of these networks:
- 18.104.22.168/24, 22.214.171.124/24 – previously originated by NYFIX, INC (AS20282) (but registered to Trinitech Systems, Inc.), via UUNet (AS701) and Level(3) (AS3356). NYFIX hasn’t appeared downstream of Con Edison any time in the last month.
- 126.96.36.199/24,188.8.131.52/24 – previously originated by Claren Road Asset Management, LLC (AS19277) via Cogent.
- 184.108.40.206/24 – previously originated by MacKay Shields,LLC (AS31860) via Time Warner Telecom.
- 220.127.116.11/20 (including 18.104.22.168/24, 22.214.171.124/24, 126.96.36.199/24, 188.8.131.52/24, 184.108.40.206/24) – previously originated by Advanced Digital Internet, Inc (AS23011) via eLink Coms (AS12006).
- 220.127.116.11/24 – previously originated by Insurance Information Institute (AS30359) via Verizon Internet Services (AS19262) (also connected to AT&T).
- 18.104.22.168/24 – previously originated by RHODES ASSOCIATES EXECUTIVE SEARCH, INC. (AS33313) via US Cybersites (AS6221) and AT&T.
- 22.214.171.124/16 – previously originated by Panix Public Access Internet (AS2033) via Cogent and Level (3).
- 126.96.36.199/20 (including 188.8.131.52/24, 184.108.40.206/24,220.127.116.11/24, 18.104.22.168/24, 22.214.171.124/24, 126.96.36.199/24) – not previously originated, registered to Track Data Corporation and covered by UUNet 188.8.131.52/16.
- 184.108.40.206/24 – not previously originated, owned by Sprint and covered by 220.127.116.11/11.
- 18.104.22.168/24 – not previously originated but registered to World Dot Com, Inc.
- 22.214.171.124/18, 126.96.36.199/19, 188.8.131.52/19 – previously originated by Walrus Internet (AS7169) via Level (3) and Cogent.
Here is a list of customer-owned networks that Con Edison announced during the event. It’s impossible to say for sure, but it’s likely that these did not cause outages for most of the real network owners:
- 184.108.40.206/24 – previously originated by Martha Stewart (AS11570) via AT&T (AS7018) and Con Edison
- 220.127.116.11/24 – previously originated by View Trade Securities (AS23004) via Qwest (AS209), Cogent (AS174) and Con Edison
- 18.104.22.168/24 – previously originated by Folksamerica (AS26913) via Sprint (AS1239) and Con Edison
- 22.214.171.124/24 – not previously originated, inside Con Edison Communications (126.96.36.199/20)
- 188.8.131.52/24 – not previously originated, inside Con Edison Communications (184.108.40.206/20)
- 220.127.116.11/24 – previously originated by Overseas Media (AS33477) via Time Warner Telecom (AS4323). Overseas is downstream of Con Edison.
- 18.104.22.168/24 – previously originated by VIEWTRADE SECURITIES (AS23004) (although the prefix is borrowed from Qwest) via Cogent (AS174). View Trade is downstream of Qwest, Cogent and Con Edison.
- 22.214.171.124/24 – previously originated by STERLING NATIONAL BANK (AS19758) via UUNet, Time Warner Telecom and Con Edison.
- 126.96.36.199/24, 188.8.131.52/21 (including 184.108.40.206/24, 220.127.116.11/24, 18.104.22.168/24, 22.214.171.124/24, 126.96.36.199/24, 188.8.131.52/24, 184.108.40.206/24, 220.127.116.11/24) – previously originated by Lava Trading, INC. (AS35967) via UUnet and Con Edison.
- 18.104.22.168/24 – previously originated by Folksamerica (AS26913) via Con Edison (although Folksamerica is also connected to Sprint).
- 22.214.171.124/24,126.96.36.199/24 – previously originated by TheStreet.Com (AS14732) via US Cybersites and Con Edison.
- 188.8.131.52/24,184.108.40.206/24,220.127.116.11/24 – previously originated by Tullett & Tokyo Forex, Inc. (AS20179) via Cogent and Internap (AS10910) (although AS20179 is downstream of Con Edison).
- 18.104.22.168/24 – previously originated by FTEN, Inc. (AS33584) via Yipes (AS6517) and Con Edison.
- 22.214.171.124/24 – previously originated by New York Daily News, L.P. (AS33535) via Global Crossing (AS3549) and Con Edison.
- 126.96.36.199/24 – prefix borrowed from UUNet, previously originated by Kohn Pedersen Fox (AS30430) via UUNet and Con Edison.
- 188.8.131.52/20, 184.108.40.206/24, 220.127.116.11/24 – previously originated by Knight Capital Group, Inc (AS22190) via UUNet, although Knight Capital Group is also downstream of Con Edison.
- 18.104.22.168/24 – previously originated by Securities Dealing Systems, Inc. (AS12265) via Internap and Con Edison.
Why did this happen? Probably someone at Con Edison made a mistake, although this series of events is messy and complicated enough that it’s hard to imagine exactly what kind of mistake it could have been. Perhaps they’ll comment here or on the NANOG mailing list. Probably not.
Although distressing, this kind of event is not that uncommon. The core routing of the Internet, as it is deployed, has few automated mechanisms to prevent this kind of foolishness. Certainly, UUNet and Verio should have known better. They should have refused to propagate the misinformation being spread by their customer. And the rest of us should have known better as well. Why does the entire internet believe these kinds of lies every time they are spread into the global routing table? That’s rhetorical, I know the answer. It’s right above in this very paragraph: there are few automated mechanisms to prevent it. With service providers running on zero, resources don’t get allocated to fix this stuff.
It makes one a little bit philosophical. The openness and flexibility of the Internet is what has allowed it to grow so quickly. It is what has allowed so many people to do so many wonderful things with it. But the legacy of that openness and flexibility remains to this day at the core of the Internet. And on days like today, that core looks a little bit rotten.
Update 2006-01-23 12:07: Manish Karir of Merit has posted a nice writeup of some of the raw data involved in this event. For those of who who are quibbling to me in private about the formatting and level of detail in this write-up, please see that one. 🙂 You can also use the BGP Inspect Tool to look at the Panix prefix and the other prefixes involved in the event.
It has been suggested that these prefixes may all be from former Con Edison customers and that failure to update the relevant Internet Routing Registry may be to blame. I haven’t had time to look at that theory yet. It certainly would explain why Verio (NTT America) would accept prefixes that don’t rightfully belong to a customer, since Verio is known for being strict about building filters from routing registries.