7 Mar
2012
7 Mar
'12
2:23 a.m.
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 away 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 peers to any number of other upstreams and the cogent route had been remarkably uncongested previously so it is sad to see it disappear. Thanks, John @ AS11404.