I e-mailed Galaxy DSL's customer support, including the traceroutes, and they somehow fixed the problem. Now I can get to the site just fine, and my traceroute looks like this:
1 192.168.100.1 (192.168.100.1) 1.054 ms 0.320 ms 0.346 ms
2 206.40.162.1 (206.40.162.1) 30.025 ms 25.708 ms 27.940 ms
3 gis-gate.gis.net (208.218.128.1) 28.025 ms 28.179 ms 29.983 ms
4 ge-7-10.car1.boston1.level3.net (4.53.48.65) 29.936 ms 27.660 ms 33.885 ms
5 ae-2-7.bar1.boston1.level3.net (4.69.132.242) 90.002 ms 27.614 ms 29.956 ms
6 ae-0-11.bar2.boston1.level3.net (4.69.140.90) 77.959 ms 35.491 ms 31.926 ms
7 ae-8-8.ebr1.newyork1.level3.net (4.69.140.98) 31.984 ms 31.654 ms 33.855 ms
8 ae-4-4.ebr1.newyork2.level3.net (4.69.141.18) 33.958 ms 33.641 ms 33.979 ms
9 * * *
10 er1-tengig-8-3.newyork.savvis.net (208.174.224.133) 35.408 ms 37.571 ms 35.831 ms
11 204.70.206.50 (204.70.206.50) 33.581 ms * *
12 hr2-ten-12-0-1.weehawkennj2.savvis.net (64.14.54.158) 33.262 ms 33.614 ms 33.963 ms
13 hr1-ten-1-0-0.jerseycitynj1.savvis.net (204.70.196.74) 35.864 ms 35.553 ms 33.927 ms
14 hr2-ten-1-0-1.jerseycitynj1.savvis.net (204.70.196.78) 33.927 ms 31.757 ms 33.811 ms
15 er1-ten-2-0-0.newyorknyd.savvis.net (204.70.196.89) 35.945 ms 35.496 ms 33.861 ms
16 208.175.194.10 (208.175.194.10) 33.945 ms 35.763 ms 33.760 ms
17 static-209-113-138-129.ngn.onecommunications.net (209.113.138.129) 43.876 ms 41.539 ms 43.995 ms
18 * *^C
Edit: They sent me an explanation, which I've added to the end of the original post.
no subject
Date: 2011-03-10 10:20 pm (UTC)Edit: They sent me an explanation, which I've added to the end of the original post.