kyle_m187
join:2006-08-02
Anchorage, AK
| Latency/Ping Problem
Hi. I have a cable internet 3mb/256k speed. I play online gaming (counterstrike) and I'm having latency problems. We have router in the house and my computer uses a wireless usb adapter. When im using my own internet connection, my ping is really high (120 - 250). but when i get signal from neighbors internet and use it, the ping is much better (90 - 120). i did a tracert of both connection and they have the same route they use. here is my connection's tracert:
Tracing route to a.4c.1243.static.theplanet.com [67.18.76.10]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 107 ms 34 ms 10 ms 81-188-165-209.gci.net [209.165.188.81]
4 20 ms 52 ms 24 ms 33-128-165-209.gci.net [209.165.128.33]
5 18 ms 148 ms 9 ms 9-128-165-209.gci.net [209.165.128.9]
6 44 ms 43 ms 41 ms 182-129-165-209.gci.net [209.165.129.182]
7 49 ms 63 ms 59 ms 209-129-165-209.gci.net [209.165.129.209]
8 103 ms 115 ms 100 ms 500.POS1-1.GW5.SEA1.ALTER.NET [157.130.191.1]
9 51 ms 132 ms 37 ms 132.ATM2-0.XR1.SEA1.ALTER.NET [152.63.106.146]
10 46 ms 44 ms 42 ms 0.so-0-0-0.XL1.SEA1.ALTER.NET [152.63.106.225]
11 125 ms 169 ms 156 ms 0.so-3-0-0.XL1.DFW13.ALTER.NET [152.63.98.121]
12 102 ms 162 ms 138 ms POS6-0.GW1.DFW13.ALTER.NET [152.63.103.85]
13 133 ms 143 ms 107 ms theplanet-gw.customer.alter.net [157.130.143.226
]
14 134 ms 139 ms 121 ms vl32.dsr02.dllstx3.theplanet.com [70.85.127.62]
15 139 ms 147 ms 121 ms vl22.dsr02.dllstx2.theplanet.com [70.85.127.76]
16 187 ms 119 ms 165 ms vl2.car04.dllstx2.theplanet.com [12.96.160.46]
17 260 ms 128 ms 114 ms a.4c.1243.static.theplanet.com [67.18.76.10]
Trace complete.
AND HERE'S USING MY NEIGHBORS INTERNET CONNECTION:
Tracing route to a.4c.1243.static.theplanet.com [67.18.76.10]
over a maximum of 30 hops:
1 * * * Request timed out.
2 10 ms 15 ms 14 ms 81-188-165-209.gci.net [209.165.188.81]
3 12 ms 18 ms 16 ms 33-128-165-209.gci.net [209.165.128.33]
4 11 ms 20 ms 15 ms 9-128-165-209.gci.net [209.165.128.9]
5 53 ms 50 ms 41 ms 202-129-165-209.gci.net [209.165.129.202]
6 37 ms 42 ms 40 ms 209-129-165-209.gci.net [209.165.129.209]
7 49 ms 41 ms 41 ms 500.POS1-1.GW5.SEA1.ALTER.NET [157.130.191.1]
8 37 ms 42 ms 50 ms 132.ATM2-0.XR1.SEA1.ALTER.NET [152.63.106.146]
9 38 ms 41 ms 38 ms 0.so-0-0-0.XL1.SEA1.ALTER.NET [152.63.106.225]
10 102 ms 105 ms 104 ms 0.so-3-0-0.XL1.DFW13.ALTER.NET [152.63.98.121]
11 103 ms 118 ms 109 ms POS6-0.GW1.DFW13.ALTER.NET [152.63.103.85]
12 116 ms 104 ms 102 ms theplanet-gw.customer.alter.net [157.130.143.226
]
13 176 ms 169 ms 217 ms vl32.dsr02.dllstx3.theplanet.com [70.85.127.62]
14 106 ms 106 ms 105 ms vl22.dsr02.dllstx2.theplanet.com [70.85.127.76]
15 106 ms 106 ms 107 ms vl2.car04.dllstx2.theplanet.com [12.96.160.46]
16 104 ms 128 ms 112 ms a.4c.1243.static.theplanet.com [67.18.76.10]
Trace complete.
Can anyone pls help me if there's any solution to this issue? I tried calling my isp provider but they cannot figure out themselves which is frustrating. Thank you in advance. |
|
sluzbenik
join:2004-08-21
Silver Spring, MD
| Hi Kyle, I am having the same issue in Battlefield 2, and my first hop also times out like that. Funny enough I used the same server to ping.
Tracing route to 5.62.344a.static.theplanet.com [74.52.98.5]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 10 ms 10 ms ge-4-16-ur02.rockville.md.bad.comcast.net [68.87.136.69]
4 9 ms 10 ms 11 ms te-9-1-ur01.rockville.md.bad.comcast.net [68.87.129.153]
5 10 ms 10 ms 10 ms te-9-1-ur01.chillum.dc.bad.comcast.net [68.87.128.217]
6 12 ms 10 ms 16 ms te-9-1-ur01.michiganave.dc.bad.comcast.net [68.87.128.210]
7 10 ms 16 ms 10 ms te-9-1-ur01.benning.dc.bad.comcast.net [68.87.128.165]
8 13 ms 13 ms 13 ms te-7-2-ar01.capitolhghts.md.bad.comcast.net [68.87.128.174]
9 13 ms 13 ms 13 ms pos-2-0-cr01.ritchieroad.md.core.comcast.net [68.87.16.153]
10 22 ms 21 ms 21 ms 12.126.168.5
11 58 ms 57 ms 56 ms tbr1-p012201.wswdc.ip.att.net [12.123.8.18]
12 59 ms 60 ms 60 ms tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
13 55 ms 54 ms 54 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
14 55 ms 57 ms 57 ms gar1-p3100.dlrtx.ip.att.net [12.123.16.165]
15 54 ms 55 ms 55 ms 12.119.136.18
16 58 ms 60 ms 57 ms vl32.dsr02.dllstx3.theplanet.com [70.85.127.62]
17 58 ms 57 ms 58 ms vl21.dsr01.dllstx2.theplanet.com [70.85.127.67]
18 63 ms 63 ms 64 ms vl1.car02.dllstx6.theplanet.com [12.96.160.23]
19 55 ms 55 ms 56 ms 5.62.344a.static.theplanet.com [74.52.98.5]
I am pretty irritated, if I knew cable was going to be this bad I would have stuck with DSL. It was great for playing games... |
|
JeepMatt
Delaware Fios
Premium
join:2001-12-28
Wilmington, DE
 ·Verizon FIOS
| Kyle-
In regards to the comparison between your trace & the neighbors, it would look like there may be an issue with your house's wiring - or the wiring from your house to the tap. With your neighbor seeing much better times, i'd point to that and have a tech out to check.
Sluz-
Your 2nd hop is your CMTS, which is set to not respond.
Your tracert is great. You're going from MD to TX across a number of ISP's in 55ms.
Not sure where the problem is.
--
"ONE team - ONE city - ONE dream!!" |
|
jervin123
join:2005-04-14
Philadelphia, PA | reply to kyle_m187
Well also your in Alaska I can tell by your traceroute so that might be part of the problem. traffic between anywhere and alaska seems to get alot of extra latency. |
|
kyle_m187
join:2006-08-02
Anchorage, AK
| reply to JeepMatt
hi phil
my isp asked me to test my speed in our own speedtest site here in alaska and see if i will get 3mb. they said if i got 3mb, then there's no problem with any wirings here. so i tried it and it was 3mb. they said im getting good signal and there's no problem with my wirings. now i dont know what to do anymore. i am so sad about this. thanks for helping phil i appreciate it so much! |
|
da sponge
join:2005-04-12
Philadelphia, PA
| reply to JeepMatt
Why is the CMTS set not to respond? That's been a relatively recent development for me - I used to be able to fire off traceroutes and have them return back without any timeouts. It's not really a problem as my connection has been fine, but I'm curious. |
|
otso32
join:2006-06-22
Anchorage, AK
| reply to kyle_m187
I think those missing hops are the gateways, not the CMTS. There are multiple CMTS's in Anchorage for both cable modems and GCI's new Digital Local Phone Service (DLPS = VoIP without the internet), but even more gateways that lead to the distribution network. Because the return path back can come through any of the gateways via the individual's CMTS, it cannot report a proper IP address for the same hop. The gateways themselves are pingable - mine is 69.178.0.1, but since it's a single host and destination, there is only one path, and so it responds to ping.
It's an extra hop, but a necessary one. At least it doesn't add a ton of latency to the connection.  |
|
