Cogent now peering with Sprint?

I never thought Sprint would ever renew its relationship with Sprint:

Tracing the route to portus.netsecdesign.com (66.6.208.6)

   1 sl-bb24-rly-9-0.sprintlink.net (144.232.14.122) 0 msec 0 msec 0
msec
   2 sl-st22-ash-6-0.sprintlink.net (144.232.20.189) 0 msec 4 msec 0
msec
   3 p15-2.core01.iad01.atlas.cogentco.com (154.54.13.61) [AS 174] 4
msec 4 msec 0 msec
   4 v3492-mpd01.iad01.atlas.cogentco.com (154.54.3.222) [AS 174] 16
msec 80 msec 196 msec
   5 v3497.mpd01.dca01.atlas.cogentco.com (154.54.5.65) [AS 174] 4 msec
4 msec 4 msec
   6 t9-3.mpd01.iah01.atlas.cogentco.com (154.54.2.222) [AS 174] 44 msec
44 msec 48 msec
   7 t2-3.mpd01.lax01.atlas.cogentco.com (154.54.3.186) [AS 174] 72 msec
72 msec 72 msec
   8 g2-0-0.core01.lax01.atlas.cogentco.com (154.54.2.101) [AS 174] 72
msec 72 msec 72 msec
   9 g49.ba01.b002698-1.lax01.atlas.cogentco.com (66.250.12.130) [AS
174] 72 msec 72 msec 72 msec
  10 PAJO-Networks.demarc.cogentco.com (38.112.9.190) [AS 174] 72 msec
76 msec 72 msec
  11 dcap04.pcap.lax01.tierzero.net (216.31.128.14) [AS 11509] 72 msec
76 msec 72 msec
  12 mmic-gw.dcap6.lax.us.tierzero.net (216.31.188.94) [AS 11509] 76
msec 80 msec 80 msec
  13 dazedandconfused.netsecdesign.com (66.6.208.4) [AS 11509] 84 msec
84 msec 88 msec
  14 portus.netsecdesign.com (66.6.208.6) [AS 11509] 84 msec 84 msec 88
msec

Next I will see pigs flying :slight_smile: Wonder how long it will last based on
Cogent's past behavior as noted here.

Edward Ray

I've not watched here closely for a number of years, but I now have a Sprint connected customer who is hating life and Cogent seems to be part of the equation. Can someone fill me in on the history of their relationship?

neal, all,

I've not watched here closely for a number of years, but I now have a
Sprint connected customer who is hating life and Cogent seems to be part
of the equation. Can someone fill me in on the history of their
relationship?

they used not to peer and cogent reached sprint via ntt america
(verio). now they are directly connected (at least in north america
for north american routes).

the routing situation is evolving and may have changed since last i
wrote about it at:

http://www.renesys.com/blog/2006/11/sprint_and_cogent_peer.shtml

(there's some path detail in that posting including stuff about when
the most recent change took place and what kind of prefixes are
carried on the adjacency. there's nothing in there about the quality
of either network or the capacity of the interconnection).

t.