Cogent peering issues with Sprint
Basil Kruglov
basil at cifnet.com
Wed Oct 10 14:51:16 UTC 2007
On Wed, Oct 10, 2007 at 09:38:42AM -0500, CARL.P.HIRSCH at sargentlundy.com wrote:
> Cogent is experiencing two problems right now. Their automated message
> reports that they have a backbone problem causing latency, but they also
> seem to be experiencing peering problems with Sprint.
>
> 2 g1-0.core01.ord01.atlas.cogentco.com (66.28.6.73) [AS 174] 0 msec 0
> msec 0 msec
> 3 t4-1.mpd01.ord01.atlas.cogentco.com (154.54.1.98) [AS 174] 4 msec 0
> msec 0 msec
> 4 v3488.mpd01.ord03.atlas.cogentco.com (154.54.5.26) [AS 174] 0 msec 0
> msec 0msec
> 5 g6-0-0-3492.core01.ord03.atlas.cogentco.com (154.54.3.241) [AS 174] 0
> msec 0 msec 0 msec
> 6 sprint.ord03.atlas.cogentco.com (154.54.13.46) [AS 174] 0 msec 4 msec
> 0 msec
> 7 sl-bb20-chi-4-0.sprintlink.net (144.232.8.218) [AS 174] 0 msec 0 msec
> 0 msec
> 8 sl-bb21-chi-15-0.sprintlink.net (144.232.26.2) [AS 174] 4 msec 4 msec
> 0 msec
> 9 sl-bb25-chi-13-0.sprintlink.net (144.232.26.90) [AS 174] 0 msec 0 msec
> 0 msec
> 10 * * *
> 11 * * *
> 12 * * *
> 13 * * *
> 14 * *
We're actually seeing the same isses @ NTT/AS2914 peering with
Sprint/AS1239:
traceroute to www.sprint.net (199.0.234.48), 64 hops max, 40 byte packets
1 10.30.1.1 (10.30.1.1) 0.504 ms 0.221 ms 0.234 ms
2 ge-2-2-0.r00.chcgil08.us.bb.gin.ntt.net (129.250.208.1) 0.298 ms 0.290
ms 0.284 ms
3 p16-0-2-3.r21.chcgil09.us.bb.gin.ntt.net (129.250.3.17) 0.469 ms 0.474
ms 0.452 ms
4 ae-0.r20.chcgil09.us.bb.gin.ntt.net (129.250.3.97) 0.423 ms 0.421 ms
0.418 ms
5 sl-st21-chi-14-1-1.sprintlink.net (144.232.8.221) 0.408 ms 0.439 ms
0.414 ms
6 sl-crs2-chi-0-0-0-3.sprintlink.net (144.232.26.9) 1.661 ms 1.521 ms
1.407 ms
7 sl-bb25-chi-8-0.sprintlink.net (144.232.26.113) 1.264 ms 1.212 ms
1.075 ms
8 * * *
^C
-Basil @ CIFNet
More information about the NANOG
mailing list