AT&T Trouble

Thu Jan 3 14:33:56 UTC 2002

AT&T master ticket 74372, they think they have a peering issue...

It was effecting our datacenter connectivity between Texas and London.

traceroute to 212.100.224.13 (212.100.224.13), 30 hops max, 38 byte packets
 1  aggr1.rackspace.com (64.39.30.130)  0.646 ms  0.532 ms  0.493 ms
 2  ge4-0.edge2.sat.rackspace.com (64.39.2.38)  0.642 ms  0.483 ms  0.434 ms
 3  12.124.219.57 (12.124.219.57)  2.088 ms  1.978 ms  1.927 ms
 4  gbr1-p70.auttx.ip.att.net (12.123.133.22)  2.150 ms  2.005 ms  1.990 ms
 5  gbr4-p10.dlstx.ip.att.net (12.122.2.109)  5.857 ms  5.864 ms  5.793 ms
 6  gbr3-p60.dlstx.ip.att.net (12.122.1.137)  5.990 ms  6.150 ms  5.791 ms
 7  gbr4-p40.attga.ip.att.net (12.122.3.38)  19.668 ms  19.610 ms  19.619 ms
 8  gbr4-p30.wswdc.ip.att.net (12.122.2.226)  33.095 ms  32.993 ms  32.970 ms

 9  * * *
10  * * *
11  * * *

----------------

traceroute to 216.239.33.101 (216.239.33.101), 30 hops max, 38 byte packets
 1  aggr1.rackspace.com (64.39.30.130)  0.675 ms  0.548 ms  0.490 ms
 2  ge4-0.edge2.sat.rackspace.com (64.39.2.38)  0.483 ms  0.478 ms  0.424 ms
 3  12.124.219.57 (12.124.219.57)  2.061 ms  1.959 ms  1.939 ms
 4  gbr1-p70.auttx.ip.att.net (12.123.133.22)  2.048 ms  2.000 ms  1.978 ms
 5  gbr4-p10.dlstx.ip.att.net (12.122.2.109)  5.805 ms  6.225 ms  5.777 ms
 6  ggr1-p370.dlstx.ip.att.net (12.123.16.245)  5.924 ms  5.905 ms  5.849 ms
 7  ibr01-p0-3.ftwo01.exodus.net (209.185.249.177)  9.324 ms  9.374 ms  9.326
ms
 8  bbr01-g2-0.ftwo01.exodus.net (216.39.64.1)  9.513 ms  9.501 ms  9.381 ms
 9  bbr01-p5-0.sntc04.exodus.net (209.185.9.109)  49.550 ms  49.550 ms
49.527 ms
10  bbr02-p7-0.sntc03.exodus.net (209.185.9.245)  49.772 ms  49.752 ms
49.794 ms
11  dcr03-g6-2.sntc03.exodus.net (216.33.153.99)  49.663 ms  49.764 ms
49.621 ms
12  csr01-ve240.sntc03.exodus.net (216.33.153.197)  50.137 ms  50.078 ms
50.062 ms
13  64.68.64.210 (64.68.64.210)  50.135 ms  50.131 ms  50.050 ms
14  exbi1-gige-1-3.google.com (216.239.47.2)  51.379 ms  51.462 ms  51.226 ms

Ian A Finlay wrote:

> Anyone know why?
>
> -Ian
>
> bash-2.04$ traceroute -I www.google.com
> traceroute to www.google.com (216.239.33.101), 30 hops max, 40 byte
> packets
>  1  CYH-A100-VL10.GW.CMU.NET (128.2.10.254)  0.765 ms  0.435 ms  0.422 ms
>  2  HYPER-VL255.GW.CMU.NET (128.2.255.7)  0.462 ms  0.466 ms  0.461 ms
>  3  bar-cmu-g4-0-0-0.psc.net (192.88.115.181)  0.343 ms  0.318 ms  0.315
> ms
>  4  nss5-foo.psc.net (192.88.115.3)  4.522 ms  4.253 ms  5.003 ms
>  5  12.124.235.73 (12.124.235.73)  15.778 ms  14.019 ms  12.569 ms
>  6  gbr2-p70.wswdc.ip.att.net (12.123.9.46)  13.540 ms  13.694 ms  13.477
> ms
>  7  12.122.11.161 (12.122.11.161)  31.691 ms  15.734 ms  16.668 ms
>  8  * * *

--
Tom Sands
Chief Network Engineer
RackSpace Managed Hosting
tsands at rackspace.com
(210)892-4000