Maybe its just _scary_ Halloween routing? It works from my view of SBC/Ameritech... even though it looks like its going through a Cisco Systems customer connection. 6 ex1-g9-0-0.pxatga.sbcglobal.net (151.164.249.9) 17.078 ms 16.964 ms 16.89 1 ms 7 bb2-p3-0.atlnga.sbcglobal.net (151.164.42.14) 17.586 ms 75.782 ms 17.365 ms 8 bb1-p14-0.atlnga.sbcglobal.net (151.164.189.21) 17.599 ms 17.469 ms 17.37 0 ms 9 core1-p5-0.cratga.sbcglobal.net (151.164.40.230) 17.232 ms 17.243 ms 17.2 13 ms 10 core3-p3-0.crchil.sbcglobal.net (151.164.241.122) 31.975 ms 31.739 ms 31. 704 ms 11 core1-p9-0.crchil.sbcglobal.net (151.164.243.18) 32.315 ms 32.086 ms 31.9 77 ms 12 bb1-p6-0.chcgil.ameritech.net (151.164.42.184) 66.854 ms 33.085 ms 110.77 5 ms 13 ded2-g1-3-0.chcgil.ameritech.net (151.164.241.113) 33.132 ms 64.020 ms 33 .133 ms 14 Cisco-Systems-1054141.cust-rtr.ameritech.net (65.42.139.42) 41.344 ms 37.3 96 ms 37.158 ms Happy Halloween, Deepak Christopher L. Morrow wrote:
On Mon, 31 Oct 2005, Roy Arends wrote:
On Mon, 31 Oct 2005, matthew zeier wrote:
Unable to geto to www.cymru.com and 68.22.187.24 has been down for 5+ hours. Known issue?
www.cymru.com resolves to 68.22.187.27 which is reachable from AS1103.
just to through more fuel on the fire, from a 701 perspective it hops though savvis and dies here:
11 acr2-so-1-0-0.Chicago.savvis.net (208.172.3.86) 25.014 ms 24.956 ms 25.833 ms 12 s228110-1.savvis-internet.uschcg1-bsn.savvis.net (64.240.84.82) 30.395 ms 29.377 ms 29.371 ms 13 *^C
I think this is the upstream device to the 'customer' network... perhaps firewall problems? or a local host problem. Generally they are pretty quick to fix these sorts of things.