Again, the common element in the timeouts seem to be sbcglobal _not_ comcast. $ traceroute havanatimes.org traceroute to havanatimes.org (81.169.145.156), 64 hops max, 40 byte packets ... 3 108-85-132-3.lightspeed.austtx.sbcglobal.net (108.85.132.3) 27.394 ms 23.129 ms 23.454 ms 4 75.8.128.82 (75.8.128.82) 24.498 ms * * 5 75.8.128.26 (75.8.128.26) 26.134 ms 23.820 ms 23.206 ms 6 * * * 7 12.83.68.141 (12.83.68.141) 23.601 ms 22.763 ms 23.122 ms 8 * * * 9 * * * 10 * * * ... and this just in, from Houston. traceroute to havanatimes.org (81.169.145.156), 64 hops max, 40 byte packets [skipping my internal firewalls] 3 99-116-244-2.lightspeed.hstntx.sbcglobal.net (99.116.244.2) 15.049 ms 13.259 ms 15.272 ms 4 * 71.144.128.132 (71.144.128.132) 12.526 ms 13.189 ms 5 * * * 6 12.83.36.1 (12.83.36.1) 14.793 ms 12.83.86.93 (12.83.86.93) 12.256 ms 10.375 ms 7 * * * 8 * * * 9 * * * 10 * * * ... from the same site in Houston, but going through Comcast: It's fine from Comcast in Houston. 3 te-5-6-ur01.royalton.tx.houston.comcast.net (68.85.250.97) 8.520 ms 9.263 ms 7.439 ms [skipping a zillion internal comcast hops] 11 80.150.169.197 (80.150.169.197) 52.592 ms 58.171 ms 61.386 ms 12 f-ed3-i.F.DE.NET.DTAG.DE (62.154.14.190) 148.515 ms 198.582 ms 134.282 ms 13 xe-3-0-1.atuin.as6724.net (62.157.249.198) 135.565 ms 135.564 ms 135.349 ms 14 xe-10-3-0.morla.as6724.net (81.169.144.33) 136.368 ms 137.703 ms 136.021 ms 15 te4-2.fiddlersriddle.as6724.net (81.169.144.34) 138.861 ms 137.925 ms 139.025 ms 16 w9c.rzone.de (81.169.145.156) 139.272 ms 138.359 ms 140.591 ms Friends in Alaska and NJ can get through (but not if they use sbcglobal routers as their first hop). Fargo, ND times out as well. On Sat, Mar 24, 2012 at 2:41 PM, C. A. Fillekes <cfillekes@gmail.com> wrote:
Reports from around the country are that traceroutes through sbcglobal (in Austin, Houston and NJ) are failing with timeout to havanatimes.org -- yet when we go in through TOR or Comcast or using overseas services, their routing is just fine. What gives?