lol, heres the traceroute anyway:
1 206.117.161.1 (206.117.161.1) 0.639 ms 0.885 ms
2 isi-acg.ln.net (130.152.136.1) 2.434 ms 2.412 ms
3 usc-isi-atm.ln.net (130.152.128.2) 3.319 ms 5.400 ms
4 fa-0-0-0.a01.lsanca01.us.ra.verio.net (209.189.66.65) 3.467 ms 3.771 ms
5 ge-6-2-0.r00.lsanca01.us.bb.verio.net (129.250.29.126) 4.132 ms 3.775 ms
6 p4-1-3-0.r01.snjsca03.us.bb.verio.net (129.250.2.113) 11.174 ms 11.899 ms
7 p4-1-0.r00.snjsca03.us.bb.verio.net (129.250.2.225) 11.469 ms 11.204 ms
8 qwest.p1-2-3.r00.snjsca03.us.bb.verio.net (129.250.9.62) 14.149 ms 14.668 ms
9 sjo-core-01.inet.qwest.net (205.171.22.118) 14.379 ms 14.673 ms
10 svl-core-01.inet.qwest.net (205.171.5.97) 14.675 ms 15.147 ms
11 svl-core-03.inet.qwest.net (205.171.14.122) 14.864 ms 14.465 ms
12 kcm-core-01.inet.qwest.net (205.171.8.138) 49.538 ms 50.415 ms
13 kcm-edge-01.inet.qwest.net (205.171.29.18) 49.723 ms 50.295 ms
14 63.150.224.46 (63.150.224.46) 52.154 ms 52.641 ms
15 border1.idir.net (209.242.64.1) 250.217 ms 64.218 ms
16 Wichita-atm2-0-KC.idir.net (209.172.198.130) 98.692 ms 98.778 ms
17 209.242.115.3 (209.242.115.3) 98.882 ms 99.401 ms
i'd agree with Technics, it must be an server problem. Nothings wrong with the connection
Originally posted by Technics
They have a lot of downtime due to the fact they cram so many accounts on to one server.