Michael Torrie wrote: > Mr Ritter wrote: > > I couldn't get to it from home on Comcast, but my work loads it just > fine. > > Yeah, comcast is doing something fishy with it. I can reach it when I > route around the damage via my VPS.
Something fishy is going on, but I wouldn't be quite so quick to place blame. I'm getting the same error from my cable at home. A traceroute bails out after getting to their network provider (Datotel). 13 p4-0-0.MAR1.MarylandHeights-MO.us.xo.net (65.106.6.158) 166.569 ms 109.793 ms 99.375 ms 14 64.1.4.2.ptr.us.xo.net (64.1.4.2) 96.351 ms 90.967 ms 92.905 ms 15 66.236.121.50.ptr.us.xo.net (66.236.121.50) 92.391 ms 91.023 ms 93.073 ms 16 stl-c2-g1-1.datotel.com (208.82.151.10) 113.740 ms 101.180 ms 94.906 ms 17 stl-d1-g5-8.datotel.com (208.82.151.34) 94.084 ms 103.618 ms 102.130 ms 18 host125.datotel.com (208.75.82.125) 97.248 ms 105.619 ms 92.498 ms 19 * * * But on my company network it goes through Level3 instead of XO and gets there. 13 DATOTEL-LLC.car2.StLouis1.Level3.net (4.53.162.10) 42.121 ms 45.706 ms 43.391 ms 14 stl-c1-g1-1.datotel.com (208.82.151.14) 43.151 ms 42.201 ms 42.403 ms 15 stl-d1-g5-1.datotel.com (208.82.151.22) 42.284 ms 42.130 ms 43.023 ms 16 host125.datotel.com (208.75.82.125) 42.247 ms 42.098 ms 42.006 ms 17 coolestfamilyever.com (208.75.86.106) [open] 44.531 ms 42.812 ms 42.849 ms Datotel doesn't appear to have a looking glass which is a real shame, so I can't see how they're routing back. That seems the more likely source of the problem to me. The server is clearly a shared hosting site so it seems very unlikely that a couple major cable operators are blocking it. I'd be interested to see traceroutes from others. It could be that their XO connection is screwy. Corey
signature.asc
Description: OpenPGP digital signature
/* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
