I currently have qwest dsl at home (640down/256up) AND it downloads/uploads at those speeds when I run speed tests (closer to 520/180 of actual throughput). But for some reason I get crazy lag in CSS (Counter: Strike Source, any game, or individual server) I ping, which seems "abnormal" for a 640 connection.
When I ping ANY server- my first hop is less then 1ms, but the hop from my computers ip to my Local IP/GATEWAY is 78 ms... (which I think is in my house- according to the silly customer support man). From then on the hops only increase by around 30 ms to its final destination around the midwest (chi/dallas). I am using no router or firewall (besides windows, and disabling does not help), and my OS is XP.
I'm almost tempted to go hook up my modem, and take my computer out to the box outside, to see if I can eliminate that 78ms hop (which seems rather high, am i right?)
IDK, it must be something with filters in my house, or wiring or anything. BUT ANY HELP would be great.
AND by my very basic assumption, If I would get maybe 350 ping with 56k, and I "supposedly" have 640k, which is aprximately 11x faster (640/56) then my ping which would be aprximately 350 w/ 56k whould be 11x faster = 32 (350/11)
i mean, thats a real ROUGH way of putting it, but the difference between 32 and the ping im getting (which is close to 100) is THAT first hop of 70/80ish.
yeah, ideas? I already tried calling qwest, they said the problem was on my end- and I kept *****ing about it, and ultimately decided after 3 hours they might actually be right in this case.
so am I completely wrong? or what. I'll attach a ping and tracert to a game server in chicago (keep in mind, this latency happens to ALL servers so it is not a routing issue). ALONG with my modem's status screen, (pls don't hack me lol) if you think i should black out any info from that screen, pls let me know.
Pinging 126.96.36.199 with 32 bytes of data:
Reply from 188.8.131.52: bytes=32 time=94ms TTL=119
Reply from 184.108.40.206: bytes=32 time=93ms TTL=119
Reply from 220.127.116.11: bytes=32 time=91ms TTL=119
Reply from 18.104.22.168: bytes=32 time=90ms TTL=119
Ping statistics for 22.214.171.124:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 94ms, Average = 92ms
Tracing route to unknown.Chicago.velocity-servers.net [126.96.36.199]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 71 ms 70 ms 77 ms omah-dsl-gw04-196.omah.qwest.net [188.8.131.52
3 75 ms 69 ms 70 ms omah-agw1.inet.qwest.net [184.108.40.206]
4 72 ms 67 ms 70 ms oma-core-01.inet.qwest.net [220.127.116.11]
5 70 ms 69 ms 74 ms oma-core-02.inet.qwest.net [18.104.22.168]
6 86 ms 85 ms 85 ms cer-core-02.inet.qwest.net [22.214.171.124]
7 94 ms 98 ms 94 ms chp-brdr-01.inet.qwest.net [126.96.36.199]
8 99 ms 107 ms 104 ms chi-bb1-geth7-3-3-0.telia.net [188.8.131.52]
9 93 ms 98 ms 86 ms so0-2-0-250.j2.ord.scnet.net [184.108.40.206]
10 97 ms 85 ms 84 ms so2-1-0.j1.ord.scnet.net [220.127.116.11]
11 97 ms 99 ms 86 ms unknown.Chicago.velocity-servers.net [66.225.195