North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: AGIS/DIGEX
Digex can't entirely rely on ANS for AGIS connectivity, I believe. Avi > > > This is just a guess, but I suspect Digex will lose more customers if > > > they cannot connect to Agis than the other way around. However I am not > > > intimately familiar with either networks customer base. > > > > > > -Deepak. > > > > Digex has sec.gov and other .gov sites... - and a lot of other business > > historically in the DC area. Those are of interest. > > > > AGIS has a number of ISPs and some RBOCs as customers of note. > > Am I missing something? > > traceroute to web1.digex.net (205.197.247.33), 30 hops max, 40 byte packets > 1 us-cup-2.webpros.com (206.127.192.7) 8 ms 8 ms > 2 sc01-c0.MainStreet.Net (199.245.73.1) 17 ms 19 ms > 3 mae-west.agis.net (198.32.136.21) 36 ms 5 ms > 4 198.32.136.39 (198.32.136.39) 9 ms 11 ms > 5 198.32.128.67 (198.32.128.67) 13 ms 12 ms > 6 h14.t96-0.Denver.t3.ans.net (140.223.9.18) 35 ms 39 ms > 7 h11-1.t24-0.Chicago.t3.ans.net (140.223.25.21) 100 ms 101 ms > 8 h14.t40-0.Cleveland.t3.ans.net (140.223.41.9) 102 ms 96 ms > 9 h14.t48-0.Hartford.t3.ans.net (140.223.33.14) 104 ms 107 ms > 10 h11.t32-0.New-York.t3.ans.net (140.223.33.129) 107 ms 104 ms > 11 enss219.t3.ans.net (140.223.33.130) 96 ms 93 ms > 12 digex.sprintnap.net (192.157.69.42) 131 ms 129 ms > 13 phl1-core1-h1-0.atlas.digex.net (165.117.50.77) 158 ms 155 ms > 14 dca3-core1-h1-0.atlas.digex.net (165.117.50.69) 149 ms 200 ms > 15 dca1-core4-h1-0.atlas.digex.net (165.117.50.65) 228 ms 107 ms > 16 dca1-core6-f1-0.atlas.digex.net (206.205.242.1) 125 ms 126 ms > 17 web1.digex.net (205.197.247.33) 146 ms 181 ms > > % date > Tue Oct 29 18:04:44 PST 1996 > - - - - - - - - - - - - - - - - -
|