[85110] in North American Network Operators' Group
AW: Cogent/Level 3 depeering
daemon@ATHENA.MIT.EDU (John van Oppen)
Wed Oct 5 12:44:34 2005
Date: Wed, 5 Oct 2005 09:49:12 -0700
From: "John van Oppen" <john@vanoppen.com>
To: "Christopher Woodfield" <rekoil@semihuman.com>,
"Jon Lewis" <jlewis@lewis.org>
Cc: <nanog@nanog.org>
Errors-To: owner-nanog@merit.edu
I think in all the recent cases, cogent ended up buying transit from =
verio.
That was the case for access to AOL and Sprint when I turned off my =
cogent feed a week ago. I think that is also what they did with france =
telecom but I am not sure on that one as I never checked (I had other =
transit).
Thanks,
John van Oppen
-----Urspr=FCngliche Nachricht-----
Von: Christopher Woodfield [mailto:rekoil@semihuman.com]=20
Gesendet: Wednesday, October 05, 2005 9:39 AM
An: Jon Lewis
Cc: nanog@nanog.org
Betreff: Re: Cogent/Level 3 depeering
I am curious - how did prior depeering "events" wind up being =20
eventually resolved? What were the resolution times, if anyone =20
remembers?
-C
On Oct 5, 2005, at 12:32 PM, Jon Lewis wrote:
>
> In the end, both providers lose, as customers buy real Internet =20
> transit from someone else.
>
> OTOH, the industry as a whole probably gains. I have a client =20
> who's massively overprovisioned, multihomed with multiple Ts each =20
> to 3 or 4 providers now after being bitten a couple years ago when =20
> singlehomed to C&W and they depeered PSI. Funny that those PSI =20
> customers are getting screwed again now.
>
> On Wed, 5 Oct 2005, Christopher Woodfield wrote:
>
>
>>
>> Ah, the problem with playing chicken is what happens when neither =20
>> player blinks...
>>
>> -C
>>
>> On Oct 5, 2005, at 11:29 AM, Vince Hoffman wrote:
>>
>>
>>> On Wed, 5 Oct 2005, Richard A Steenbergen wrote:
>>>
>>>> A couple weeks later than expected, but as of Oct 5 02:51AM EDT =20
>>>> it looks
>>>> like 3356 and 174 are no longer reachable.
>>>> lg.level3.net:
>>>> Show Level 3 (Washington, DC) BGP routes for 38.9.51.20
>>>> No matching routes found for 38.9.51.20.
>>>> www.cogentco.com looking glass:
>>>> Tracing the route to www.Level3.com (209.245.19.42)
>>>> 1 f29.ba01.b005944-0.dca01.atlas.cogentco.com (66.250.56.189) 4 =20
>>>> msec 4 msec 0 msec
>>>> 2 * * *
>>>> 3 * * *
>>>> I guess the earlier reports of (3)'s lack of testicular =20
>>>> fortitude may have
>>>> been exagerated after all. :)
>>>>
>>> It's sure causing a few headaches here.
>>> (from level3 looking glass) Show Level 3 (London, England) BGP =20
>>> routes for 38.9.51.20
>>> No matching routes found for 38.9.51.20
>>> As of 16:22 BST Level3 still seems to have no routes for cogent's =20
>>> space. thats about 5 hours now.
>>> Vince
>>>
>>>> --=20
>>>> Richard A Steenbergen <ras@e-gerbil.net> http://www.e-=20
>>>> gerbil.net/ras
>>>> GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA =20
>>>> F8B1 2CBC)
>>>>
>>
>>
>
> ----------------------------------------------------------------------
> Jon Lewis | I route
> Senior Network Engineer | therefore you are
> Atlantic Net | _________ http://www.lewis.org/=20
> ~jlewis/pgp for PGP public key_________
>
>
