Sprint/Cogent Peering Issue?
Hi, We are seeing traffic getting dropped between our Cogent and Sprint connect DC's. One of them is getting shutdown, so we just have a Cogent link there :| Anyone seeing anything similar? From: 91.102.40.18 traceroute to ops1.scc.rnmd.net (208.91.188.136), 30 hops max, 38 byte packets 1 v1-core-sw1 (91.102.40.5) 0.471 ms 0.422 ms 0.431 ms 2 ge-0-1-0-pat2 (91.102.40.146) 0.376 ms 0.354 ms 0.335 ms 3 fe-1-3-1-501-pat1 (91.102.40.208) 0.376 ms 0.344 ms 0.407 ms 4 vl324.mpd01.lon01.atlas.cogentco.com (149.6.147.217) 0.745 ms 0.744 ms 0.740 ms 5 te3-1.mpd02.lon01.atlas.cogentco.com (130.117.2.26) 0.717 ms 39.037 ms te1-8.ccr01.lon01.atlas.cogentco.com (130.117.3.226) 0.565 ms 6 gi6-0-0.core01.lon01.atlas.cogentco.com (130.117.1.73) 0.592 ms 0.450 ms 0.483 ms 7 213.206.131.29 (213.206.131.29) 0.581 ms 0.503 ms 0.483 ms 8 sl-bb21-lon-3-0.sprintlink.net (213.206.129.152) 1.078 ms 0.905 ms 0.934 ms 9 * From 208.91.188.138 traceroute to ops2.lnc.rnmd.net (91.102.40.18), 30 hops max, 38 byte packets 1 v1-core-sw1 (208.91.188.130) 0.600 ms 0.456 ms 2.105 ms 2 f0-0-4-0-pat2 (207.0.21.114) 0.416 ms 0.466 ms 0.486 ms 3 sl-st1-sc-2-6.sprintlink.net (144.228.111.25) 0.455 ms 0.224 ms 0.236 ms 4 sl-crs2-sj-0-1-0-3.sprintlink.net (144.232.20.196) 1.482 ms 1.477 ms 1.232 ms 5 sl-st20-sj-12-0-0.sprintlink.net (144.232.20.63) 2.482 ms 2.472 ms 2.485 ms 6 po5-3.core01.sjc03.atlas.cogentco.com (154.54.13.49) 2.732 ms 2.472 ms 2.485 ms 7 te3-1.mpd01.sjc03.atlas.cogentco.com (154.54.6.85) 2.705 ms 2.723 ms 2.735 ms 8 vl3493.ccr02.sjc01.atlas.cogentco.com (154.54.6.109) 3.231 ms vl3492.mpd01.sjc01.atlas.cogentco.com (154.54.6.105) 3.227 ms vl3491.ccr02.sjc01.atlas.cogentco.com (154.54.6.101) 2.726 ms 9 te9-3.mpd01.sfo01.atlas.cogentco.com (154.54.2.53) 3.968 ms 3.722 ms te8-3.ccr02.sfo01.atlas.cogentco.com (154.54.2.137) 3.988 ms 10 te9-2.ccr02.mci01.atlas.cogentco.com (154.54.24.118) 50.943 ms te7-4.mpd01.mci01.atlas.cogentco.com (154.54.24.106) 50.944 ms 50.720 ms 11 te9-3.ccr02.ord01.atlas.cogentco.com (154.54.25.78) 50.669 ms 63.423 ms te9-3.mpd01.ord01.atlas.cogentco.com (154.54.25.82) 51.206 ms 12 te2-1.ccr02.bos01.atlas.cogentco.com (154.54.7.170) 78.172 ms te3-3.mpd01.bos01.atlas.cogentco.com (154.54.7.82) 100.666 ms te2-1.ccr02.bos01.atlas.cogentco.com (154.54.7.170) 78.176 ms 13 * * * Thanks, craig Craig Holland Rhythm NewMedia Sr. Director Operations Integration YIM: cholland
Re: Sprint/Cogent Peering Issue?
No apparent problems from Cogent in Northern Virginia : tme$ traceroute ops1.scc.rnmd.net traceroute to ops1.scc.rnmd.net (208.91.188.136), 64 hops max, 40 byte packets 1 dmz-mct2 (63.105.122.1) 0.754 ms 0.278 ms 0.485 ms 2 gi0-7.na21.b002176-1.dca01.atlas.cogentco.com (38.99.206.153) 0.741 ms 0.612 ms 0.753 ms 3 gi2-1.3587.core01.dca01.atlas.cogentco.com (38.20.32.13) 14.444 ms 0.756 ms 0.728 ms 4 te3-1.ccr02.dca01.atlas.cogentco.com (154.54.3.158) 0.980 ms 1.067 ms 0.978 ms 5 vl3493.mpd01.dca02.atlas.cogentco.com (154.54.7.230) 46.711 ms te4-1.mpd01.dca02.atlas.cogentco.com (154.54.2.182) 2.400 ms te7-3.mpd01.dca02.atlas.cogentco.com (154.54.6.26) 1.863 ms 6 vl3494.mpd01.iad01.atlas.cogentco.com (154.54.5.42) 1.935 ms vl3496.mpd01.iad01.atlas.cogentco.com (154.54.5.46) 1.968 ms vl3497.mpd01.iad01.atlas.cogentco.com (154.54.5.66) 1.618 ms 7 gi9-0-0.core01.iad01.atlas.cogentco.com (154.54.3.221) 1.578 ms gi14-0-0.core01.iad01.atlas.cogentco.com (154.54.5.57) 1.840 ms gi2-0-0.core01.iad01.atlas.cogentco.com (154.54.5.33) 1.788 ms 8 sprint.iad01.atlas.cogentco.com (154.54.13.62) 1.657 ms 1.693 ms 1.713 ms 9 sl-crs1-rly-0-4-5-0.sprintlink.net (144.232.20.154) 3.725 ms 3.597 ms 3.724 ms 10 sl-crs2-sj-0-5-0-0.sprintlink.net (144.232.20.186) 70.442 ms 70.780 ms 70.417 ms 11 sl-st1-sc-1-1.sprintlink.net (144.232.20.197) 70.672 ms 70.844 ms 70.973 ms 12 sl-rhyth2-158722-0.sprintlink.net (144.228.111.26) 71.197 ms 71.128 ms 70.935 ms 13 208.91.188.68 (208.91.188.68) 71.213 ms 71.381 ms 71.172 ms 14 ops1.scc.rnmd.net (208.91.188.136) 71.412 ms 71.497 ms 71.673 ms Regards Marshall On Sep 19, 2008, at 4:27 AM, Craig Holland wrote: Hi, We are seeing traffic getting dropped between our Cogent and Sprint connect DC's. One of them is getting shutdown, so we just have a Cogent link there :| Anyone seeing anything similar? From: 91.102.40.18 traceroute to ops1.scc.rnmd.net (208.91.188.136), 30 hops max, 38 byte packets 1 v1-core-sw1 (91.102.40.5) 0.471 ms 0.422 ms 0.431 ms 2 ge-0-1-0-pat2 (91.102.40.146) 0.376 ms 0.354 ms 0.335 ms 3 fe-1-3-1-501-pat1 (91.102.40.208) 0.376 ms 0.344 ms 0.407 ms 4 vl324.mpd01.lon01.atlas.cogentco.com (149.6.147.217) 0.745 ms 0.744 ms 0.740 ms 5 te3-1.mpd02.lon01.atlas.cogentco.com (130.117.2.26) 0.717 ms 39.037 ms te1-8.ccr01.lon01.atlas.cogentco.com (130.117.3.226) 0.565 ms 6 gi6-0-0.core01.lon01.atlas.cogentco.com (130.117.1.73) 0.592 ms 0.450 ms 0.483 ms 7 213.206.131.29 (213.206.131.29) 0.581 ms 0.503 ms 0.483 ms 8 sl-bb21-lon-3-0.sprintlink.net (213.206.129.152) 1.078 ms 0.905 ms 0.934 ms 9 * From 208.91.188.138 traceroute to ops2.lnc.rnmd.net (91.102.40.18), 30 hops max, 38 byte packets 1 v1-core-sw1 (208.91.188.130) 0.600 ms 0.456 ms 2.105 ms 2 f0-0-4-0-pat2 (207.0.21.114) 0.416 ms 0.466 ms 0.486 ms 3 sl-st1-sc-2-6.sprintlink.net (144.228.111.25) 0.455 ms 0.224 ms 0.236 ms 4 sl-crs2-sj-0-1-0-3.sprintlink.net (144.232.20.196) 1.482 ms 1.477 ms 1.232 ms 5 sl-st20-sj-12-0-0.sprintlink.net (144.232.20.63) 2.482 ms 2.472 ms 2.485 ms 6 po5-3.core01.sjc03.atlas.cogentco.com (154.54.13.49) 2.732 ms 2.472 ms 2.485 ms 7 te3-1.mpd01.sjc03.atlas.cogentco.com (154.54.6.85) 2.705 ms 2.723 ms 2.735 ms 8 vl3493.ccr02.sjc01.atlas.cogentco.com (154.54.6.109) 3.231 ms vl3492.mpd01.sjc01.atlas.cogentco.com (154.54.6.105) 3.227 ms vl3491.ccr02.sjc01.atlas.cogentco.com (154.54.6.101) 2.726 ms 9 te9-3.mpd01.sfo01.atlas.cogentco.com (154.54.2.53) 3.968 ms 3.722 ms te8-3.ccr02.sfo01.atlas.cogentco.com (154.54.2.137) 3.988 ms 10 te9-2.ccr02.mci01.atlas.cogentco.com (154.54.24.118) 50.943 ms te7-4.mpd01.mci01.atlas.cogentco.com (154.54.24.106) 50.944 ms 50.720 ms 11 te9-3.ccr02.ord01.atlas.cogentco.com (154.54.25.78) 50.669 ms 63.423 ms te9-3.mpd01.ord01.atlas.cogentco.com (154.54.25.82) 51.206 ms 12 te2-1.ccr02.bos01.atlas.cogentco.com (154.54.7.170) 78.172 ms te3-3.mpd01.bos01.atlas.cogentco.com (154.54.7.82) 100.666 ms te2-1.ccr02.bos01.atlas.cogentco.com (154.54.7.170) 78.176 ms 13 * * * Thanks, craig Craig Holland Rhythm NewMedia Sr. Director Operations Integration YIM: cholland
Re: Sprint/Cogent Peering Issue?
I'm seeing issues with traceroutes dying at Sprint in London, too. From our site here in the UK (transit from NTL Telewest Business) I can't reach cisco.com (but I know cisco.com is up - I can reach it from elsewhere). Apparently customers of XS4ALL in the Netherlands are seeing similar behaviour. -roy 1 c1-cam-gi-0-0-100 (172.16.128.2) 0.839 ms 0.470 ms 0.405 ms 2 ntl-gw1-fa-0-0 (82.1.12.129) 1.975 ms 1.804 ms 1.517 ms 3 nrth-lam-1-multilink26.network.virginmedia.net (62.253.60.221) 11.926 ms 4.612 ms 3.921 ms 4 nrth-t3core-1a-so-700-0.network.virginmedia.net (213.106.255.25) 5.102 ms 11.540 ms 9.283 ms 5 nth-bb-a-so-210-0.network.virginmedia.net (212.43.162.237) 4.833 ms 7.680 ms 5.126 ms 6 gfd-bb-b-so-010-0.network.virginmedia.net (62.253.185.98) 9.787 ms 7.746 ms 8.956 ms 7 sl-gw11-lon-11-0.sprintlink.net (213.206.156.101) 15.766 ms 12.921 ms 9.373 ms 8 sl-bb21-lon-11-0.sprintlink.net (213.206.128.58) 19.495 ms 9.444 ms 10.447 ms 9 * * * 10 * * * 11 * * *
Re: Sprint/Cogent Peering Issue?
On Fri, Sep 19, 2008 at 06:02:37AM -0400, Marshall Eubanks wrote: No apparent problems from Cogent in Northern Virginia : Fine from Cogent in DC. Not so fine from Cogent in the Netherlands. traceroute to ops1.scc.rnmd.net (208.91.188.136), 64 hops max, 40 byte packets 1 38.105.91.2 (38.105.91.2) [AS174] 0 ms 0 ms 0 ms 2 gi0-1.na32.b001806-1.dca01.atlas.cogentco.com (38.104.30.101) [AS174] 1 ms 1 ms 2 ms 3 te9-3.3596.ccr02.dca01.atlas.cogentco.com (38.20.37.209) [AS174] 0 ms 0 ms 0 ms 4 vl3493.mpd01.dca02.atlas.cogentco.com (154.54.7.230) [AS174] 1 ms te4-1.mpd01.dca02.atlas.cogentco.com (154.54.2.182) [AS174] 25 ms 94 ms 5 vl3496.mpd01.iad01.atlas.cogentco.com (154.54.5.46) [AS174] 1 ms te1-2.ccr02.iad01.atlas.cogentco.com (154.54.7.158) [AS174] 1 ms te2-2.ccr02.iad01.atlas.cogentco.com (154.54.7.162) [AS174] 1 ms 6 gi9-0-0.core01.iad01.atlas.cogentco.com (154.54.3.221) [AS174] 1 ms gi0-0-0.core01.iad01.atlas.cogentco.com (154.54.3.225) [AS174] 1 ms 1 ms 7 sprint.iad01.atlas.cogentco.com (154.54.13.62) [AS174] 1 ms 1 ms 1 ms 8 sl-crs2-rly-0-1-3-0.sprintlink.net (144.232.20.188) [AS1239] 3 ms 4 ms 3 ms 9 sl-crs2-sj-0-0-0-2.sprintlink.net (144.232.8.145) [AS1239] 70 ms 71 ms 70 ms 10 sl-st1-sc-1-1.sprintlink.net (144.232.20.197) [AS1239] 71 ms 71 ms 71 ms 11 sl-rhyth2-158722-0.sprintlink.net (144.228.111.26) [AS1239] 71 ms 71 ms 71 ms 12 208.91.188.68 (208.91.188.68) [NONE] 71 ms 71 ms 71 ms 13 ops1.scc.rnmd.net (208.91.188.136) [NONE] 71 ms 71 ms 71 ms traceroute to ops1.scc.rnmd.net (208.91.188.136), 30 hops max, 40 byte packets 1 lid-br1-g0-2-10.ops.theveniceproject.com (89.251.0.1) [AS42072] 0.428 ms 0.373 ms 0.368 ms 2 gi4-10.ccr01.ams05.atlas.cogentco.com (149.6.128.125) [AS174] 1.474 ms 1.415 ms 1.420 ms 3 te3-4.ccr01.ams03.atlas.cogentco.com (130.117.0.85) [AS174] 1.668 ms 1.734 ms 1.617 ms 4 gi2-0-0.core01.ams03.atlas.cogentco.com (130.117.0.33) [AS174] 1.573 ms 1.620 ms gi10-0-0.core01.ams03.atlas.cogentco.com (130.117.0.237) [AS174] 1.618 ms 5 sprint.ams03.atlas.cogentco.com (130.117.14.122) [AS174] 1.606 ms 1.617 ms 1.569 ms 6 sl-bb21-ams-15-0-0.sprintlink.net (217.149.32.34) [AS1239] 1.673 ms 1.721 ms 1.571 ms 7 sl-bb23-lon-4-0.sprintlink.net (213.206.129.143) [AS1239] 9.562 ms 9.500 ms 9.456 ms 8 sl-bb21-lon-13-0.sprintlink.net (213.206.128.55) [AS1239] 9.660 ms 9.628 ms 9.601 ms 9 * * * 10 * * * HTH Andrew On Sep 19, 2008, at 4:27 AM, Craig Holland wrote: Hi, We are seeing traffic getting dropped between our Cogent and Sprint connect DC's. One of them is getting shutdown, so we just have a Cogent link there :| Anyone seeing anything similar? From: 91.102.40.18 traceroute to ops1.scc.rnmd.net (208.91.188.136), 30 hops max, 38 byte packets 1 v1-core-sw1 (91.102.40.5) 0.471 ms 0.422 ms 0.431 ms 2 ge-0-1-0-pat2 (91.102.40.146) 0.376 ms 0.354 ms 0.335 ms 3 fe-1-3-1-501-pat1 (91.102.40.208) 0.376 ms 0.344 ms 0.407 ms 4 vl324.mpd01.lon01.atlas.cogentco.com (149.6.147.217) 0.745 ms 0.744 ms 0.740 ms 5 te3-1.mpd02.lon01.atlas.cogentco.com (130.117.2.26) 0.717 ms 39.037 ms te1-8.ccr01.lon01.atlas.cogentco.com (130.117.3.226) 0.565 ms 6 gi6-0-0.core01.lon01.atlas.cogentco.com (130.117.1.73) 0.592 ms 0.450 ms 0.483 ms 7 213.206.131.29 (213.206.131.29) 0.581 ms 0.503 ms 0.483 ms 8 sl-bb21-lon-3-0.sprintlink.net (213.206.129.152) 1.078 ms 0.905 ms 0.934 ms 9 * From 208.91.188.138 traceroute to ops2.lnc.rnmd.net (91.102.40.18), 30 hops max, 38 byte packets 1 v1-core-sw1 (208.91.188.130) 0.600 ms 0.456 ms 2.105 ms 2 f0-0-4-0-pat2 (207.0.21.114) 0.416 ms 0.466 ms 0.486 ms 3 sl-st1-sc-2-6.sprintlink.net (144.228.111.25) 0.455 ms 0.224 ms 0.236 ms 4 sl-crs2-sj-0-1-0-3.sprintlink.net (144.232.20.196) 1.482 ms 1.477 ms 1.232 ms 5 sl-st20-sj-12-0-0.sprintlink.net (144.232.20.63) 2.482 ms 2.472 ms 2.485 ms 6 po5-3.core01.sjc03.atlas.cogentco.com (154.54.13.49) 2.732 ms 2.472 ms 2.485 ms 7 te3-1.mpd01.sjc03.atlas.cogentco.com (154.54.6.85) 2.705 ms 2.723 ms 2.735 ms 8 vl3493.ccr02.sjc01.atlas.cogentco.com (154.54.6.109) 3.231 ms vl3492.mpd01.sjc01.atlas.cogentco.com (154.54.6.105) 3.227 ms vl3491.ccr02.sjc01.atlas.cogentco.com (154.54.6.101) 2.726 ms 9 te9-3.mpd01.sfo01.atlas.cogentco.com (154.54.2.53) 3.968 ms 3.722 ms te8-3.ccr02.sfo01.atlas.cogentco.com (154.54.2.137) 3.988 ms 10 te9-2.ccr02.mci01.atlas.cogentco.com (154.54.24.118) 50.943 ms te7-4.mpd01.mci01.atlas.cogentco.com (154.54.24.106) 50.944 ms 50.720 ms 11 te9-3.ccr02.ord01.atlas.cogentco.com (154.54.25.78) 50.669 ms 63.423 ms te9-3.mpd01.ord01.atlas.cogentco.com (154.54.25.82) 51.206 ms 12 te2-1.ccr02.bos01.atlas.cogentco.com (154.54.7.170) 78.172 ms te3-3.mpd01.bos01.atlas.cogentco.com (154.54.7.82) 100.666 ms te2-1.ccr02.bos01.atlas.cogentco.com (154.54.7.170) 78.176 ms 13 * * * Thanks, craig
Re: Sprint/Cogent Peering Issue?
FWIW, the Sprint routing issues we were seeing seem to have been resolved now, AFAICS. -roy
