[150875] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

did AS174 and AS4134 de-peer?

daemon@ATHENA.MIT.EDU (John van Oppen)
Wed Mar 7 02:24:02 2012

From: John van Oppen <jvanoppen@spectrumnet.us>
To: "nanog@nanog.org" <nanog@nanog.org>
Date: Wed, 7 Mar 2012 07:23:04 +0000
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

All -

I was noticing that it appears from our Seattle-based full route feed from =
cogent that they may have de-peered AS4134 (or vise-versa)...   anyone know=
 anything about this?    We noticed this recently in a shift of traffic awa=
y from cogent for traffic to and from china telecom...   Now cogent's path =
is _174_1239_4134_.

In any case, was just wondering if anyone had noticed this.   AS4134 is one=
 that often generates NOC calls on our end due to their often saturated pee=
rs to any number of other upstreams and the cogent route had been remarkabl=
y uncongested previously so it is sad to see it disappear.



Thanks,
John @ AS11404.

home help back first fref pref prev next nref lref last post