dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1042
share rss forum feed

ball2hi

join:2012-12-02
Anaheim, CA

1 edit

Consistent afternoon packet-loss/above-avg ping

Current service paid:
DL: 20 mbps / UP : 2 mbps (Southern California)

I've contacted customer support on both phone/online services. I've posted recently on DSLReports to Direct TWC. They're either telling me that everything looks fine from their end (After doing their fancy diagnostics and making me take a bias'd speedtest.net) or saying the issue is out of their network and thus will not continue to troubleshoot it.

As a gamer, losing packets and having abnormal 20-30ms increase at match times is not ideal in the least. Over 2 years of service, this issue has been going on/off every 3 months.

Tracert/Ping results (When there is no problems):

quote:
Chicago Gameserver:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\New>tracert 64.74.97.58

Tracing route to c-64-74-97-58.internap-chicago.nfoservers.com [64.74.97.58]
over a maximum of 30 hops:

1 37 ms 25 ms 29 ms cpe-98-151-48-1.socal.res.rr.com [98.151.48.1]
2 11 ms 12 ms 12 ms tge1-5.anhmcapj-cer01.socal.rr.com [76.166.16.33
]
3 22 ms 15 ms 23 ms tge0-8-0-11.cyprcabw-ccr01.socal.rr.com [72.129.
22.34]
4 17 ms 23 ms 15 ms 72.129.21.0
5 17 ms 23 ms 15 ms ae-5-0.cr0.lax00.tbone.rr.com [66.109.6.102]
6 16 ms 15 ms 15 ms 107.14.19.138
7 15 ms 15 ms 15 ms 107.14.16.38
8 15 ms 15 ms 16 ms cr2-tengig-0-7-4-0.lay.savvis.net [204.70.198.9]

9 94 ms 95 ms 95 ms cr2-te-0-3-0-0.chd.savvis.net [204.70.192.97]
10 95 ms 95 ms 95 ms ber2-te-4-4.chq.savvis.net [206.28.96.6]
11 81 ms 79 ms 79 ms 208.173.180.134
12 82 ms 79 ms 79 ms border5.po1-bbnet1.chg.pnap.net [64.94.32.10]
13 81 ms 80 ms 82 ms c-64-74-97-58.internap-chicago.nfoservers.com [6
4.74.97.58]

Trace complete.

C:\Users\New>ping 64.74.97.58

Pinging 64.74.97.58 with 32 bytes of data:
Reply from 64.74.97.58: bytes=32 time=79ms TTL=117
Reply from 64.74.97.58: bytes=32 time=79ms TTL=117
Reply from 64.74.97.58: bytes=32 time=81ms TTL=117
Reply from 64.74.97.58: bytes=32 time=79ms TTL=117

Ping statistics for 64.74.97.58:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 79ms, Maximum = 81ms, Average = 79ms

C:\Users\New>
quote:
Seattle Gameserver:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\New>tracert 66.150.164.211

Tracing route to c-66-150-164-211.internap-seattle.nfoservers.com [66.150.164.21
1]
over a maximum of 30 hops:

1 34 ms 27 ms 29 ms cpe-98-151-48-1.socal.res.rr.com [98.151.48.1]
2 11 ms 12 ms 12 ms tge1-5.anhmcapj-cer01.socal.rr.com [76.166.16.33
]
3 15 ms 15 ms 15 ms tge0-8-0-10.cyprcabw-ccr01.socal.rr.com [72.129.
22.32]
4 21 ms 15 ms 23 ms 72.129.21.0
5 19 ms 15 ms 15 ms 107.14.19.32
6 14 ms 15 ms 15 ms ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
7 14 ms 15 ms 32 ms 66.109.9.206
8 45 ms 41 ms 41 ms internap.tengigabitethernet3-4.ar7.sea1.gblx.net
[159.63.55.26]
9 216 ms 41 ms 41 ms border9.t8-1-bbnet2.sef.pnap.net [63.251.160.83]

10 40 ms 41 ms 41 ms c-66-150-164-211.internap-seattle.nfoservers.com
[66.150.164.211]

Trace complete.

C:\Users\New>ping 66.150.164.211

Pinging 66.150.164.211 with 32 bytes of data:
Reply from 66.150.164.211: bytes=32 time=40ms TTL=119
Reply from 66.150.164.211: bytes=32 time=41ms TTL=119
Reply from 66.150.164.211: bytes=32 time=42ms TTL=119
Reply from 66.150.164.211: bytes=32 time=41ms TTL=119

Ping statistics for 66.150.164.211:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 42ms, Average = 41ms

C:\Users\New>
quote:
Dallas Gameserver:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\System32>tracert 66.150.214.137

Tracing route to v-66-150-214-137.unman-vds.internap-dallas.nfoservers.com [66.1
50.214.137]
over a maximum of 30 hops:

1 43 ms 26 ms 29 ms cpe-98-151-48-1.socal.res.rr.com [98.151.48.1]
2 13 ms 16 ms 13 ms tge1-5.anhmcapj-cer01.socal.rr.com [76.166.16.33
]
3 23 ms 15 ms 17 ms tge0-8-0-11.cyprcabw-ccr01.socal.rr.com [72.129.
22.34]
4 19 ms 23 ms 15 ms 72.129.21.0
5 21 ms 15 ms 15 ms ae-6-0.cr0.lax00.tbone.rr.com [66.109.6.212]
6 14 ms 15 ms 15 ms 107.14.19.138
7 15 ms 18 ms 15 ms TenGigabitEthernet4-2.ar4.LAX1.gblx.net [208.50.
254.25]
8 49 ms 50 ms 51 ms INTERNAP.TenGigabitEthernet1-2.ar3.DAL2.gblx.net
[208.51.41.58]
9 50 ms 52 ms 49 ms border1.ge4-1-bbnet2.ext1a.dal.pnap.net [216.52.
191.84]
10 49 ms 50 ms 50 ms v-66-150-214-137.unman-vds.internap-dallas.nfose
rvers.com [66.150.214.137]

Trace complete.

C:\Windows\System32>ping 66.150.214.137

Pinging 66.150.214.137 with 32 bytes of data:
Reply from 66.150.214.137: bytes=32 time=50ms TTL=54
Reply from 66.150.214.137: bytes=32 time=48ms TTL=54
Reply from 66.150.214.137: bytes=32 time=49ms TTL=54
Reply from 66.150.214.137: bytes=32 time=50ms TTL=54

Ping statistics for 66.150.214.137:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 50ms, Average = 49ms

C:\Windows\System32>
quote:
Google:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\System32>tracert google.com

Tracing route to google.com [74.125.224.163]
over a maximum of 30 hops:

1 34 ms 27 ms 29 ms cpe-98-151-48-1.socal.res.rr.com [98.151.48.1]
2 9 ms 12 ms 12 ms tge1-5.anhmcapj-cer01.socal.rr.com [76.166.16.33
]
3 17 ms 23 ms 15 ms tge0-8-0-10.cyprcabw-ccr01.socal.rr.com [72.129.
22.32]
4 18 ms 15 ms 23 ms 72.129.21.0
5 21 ms 15 ms 15 ms ae-5-0.cr0.lax00.tbone.rr.com [66.109.6.102]
6 15 ms 15 ms 15 ms ae-0-0.pr0.lax10.tbone.rr.com [66.109.6.133]
7 74 ms 76 ms 76 ms 72.14.198.73
8 60 ms 38 ms 20 ms 64.233.174.238
9 14 ms 15 ms 16 ms 72.14.236.11
10 15 ms 15 ms 15 ms lax02s01-in-f3.1e100.net [74.125.224.163]

Trace complete.

C:\Windows\System32>ping google.com

Pinging google.com [74.125.224.229] with 32 bytes of data:
Reply from 74.125.224.229: bytes=32 time=14ms TTL=55
Reply from 74.125.224.229: bytes=32 time=19ms TTL=55
Reply from 74.125.224.229: bytes=32 time=19ms TTL=55
Reply from 74.125.224.229: bytes=32 time=14ms TTL=55

Ping statistics for 74.125.224.229:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 19ms, Average = 16ms

C:\Windows\System32>
Tracert/Ping results (When there is problems):
quote:
Chicago Gameserver:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\System32>tracert 64.74.97.58

Tracing route to c-64-74-97-58.internap-chicago.nfoservers.com [64.74.97.58]
over a maximum of 30 hops:

1 2930 ms 2558 ms 2279 ms cpe-98-151-48-1.socal.res.rr.com [98.151.48.1]
2 11 ms 12 ms 12 ms tge1-5.anhmcapj-cer01.socal.rr.com [76.166.16.33
]
3 17 ms 16 ms 22 ms tge0-8-0-11.cyprcabw-ccr01.socal.rr.com [72.129.
22.34]
4 22 ms 15 ms 23 ms 72.129.21.0
5 19 ms 23 ms 15 ms ae-5-0.cr0.lax00.tbone.rr.com [66.109.6.102]
6 15 ms 15 ms 12 ms 107.14.19.138
7 54 ms 200 ms 183 ms 107.14.16.38
8 16 ms 18 ms 19 ms cr2-tengig-0-7-4-0.lay.savvis.net [204.70.198.9]

9 95 ms 95 ms 98 ms cr2-te-0-3-0-0.chd.savvis.net [204.70.192.97]
10 98 ms 95 ms 95 ms ber2-te-4-4.chq.savvis.net [206.28.96.6]
11 133 ms 133 ms 135 ms 208.173.180.134
12 107 ms 104 ms 104 ms border5.po1-bbnet1.chg.pnap.net [64.94.32.10]
13 128 ms 132 ms 135 ms c-64-74-97-58.internap-chicago.nfoservers.com [6
4.74.97.58]

Trace complete.

C:\Windows\System32>ping 64.74.97.58

Pinging 64.74.97.58 with 32 bytes of data:
Reply from 64.74.97.58: bytes=32 time=133ms TTL=114
Reply from 64.74.97.58: bytes=32 time=133ms TTL=114
Reply from 64.74.97.58: bytes=32 time=130ms TTL=114
Reply from 64.74.97.58: bytes=32 time=132ms TTL=114

Ping statistics for 64.74.97.58:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 130ms, Maximum = 133ms, Average = 132ms

C:\Windows\System32>
quote:
Dallas Gameserver:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\System32>tracert 66.150.214.198

Tracing route to c-66-150-214-198.internap-dallas.nfoservers.com [66.150.214.198
]
over a maximum of 30 hops:

1 28 ms 18 ms 21 ms cpe-98-151-48-1.socal.res.rr.com [98.151.48.1]
2 8 ms 8 ms 12 ms tge1-5.anhmcapj-cer01.socal.rr.com [76.166.16.33
]
3 22 ms 23 ms 16 ms tge0-8-0-11.cyprcabw-ccr01.socal.rr.com [72.129.
22.34]
4 22 ms 23 ms 23 ms 72.129.21.0
5 27 ms 23 ms 15 ms 107.14.17.132
6 51 ms 31 ms 15 ms ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
7 16 ms 15 ms 18 ms TenGigabitEthernet1-2.ar5.LAX1.gblx.net [64.208.
205.153]
8 76 ms 59 ms 58 ms INTERNAP.TenGigabitEthernet1-2.ar3.DAL2.gblx.net
[208.51.41.58]
9 57 ms 60 ms 56 ms border1.ge1-1-bbnet1.ext1a.dal.pnap.net [216.52.
191.24]
10 59 ms 58 ms 56 ms c-66-150-214-198.internap-dallas.nfoservers.com
[66.150.214.198]

Trace complete.

C:\Windows\System32>ping 66.150.214.198

Pinging 66.150.214.198 with 32 bytes of data:
Reply from 66.150.214.198: bytes=32 time=53ms TTL=118
Reply from 66.150.214.198: bytes=32 time=56ms TTL=118
Reply from 66.150.214.198: bytes=32 time=62ms TTL=118
Reply from 66.150.214.198: bytes=32 time=76ms TTL=118

Ping statistics for 66.150.214.198:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 76ms, Average = 61ms

C:\Windows\System32>
quote:
Google:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\System32>tracert google.com

Tracing route to google.com [74.125.224.199]
over a maximum of 30 hops:

1 67 ms 64 ms 101 ms cpe-98-151-48-1.socal.res.rr.com [98.151.48.1]
2 12 ms 12 ms 12 ms tge1-5.anhmcapj-cer01.socal.rr.com [76.166.16.33
]
3 17 ms 15 ms 15 ms tge0-8-0-10.cyprcabw-ccr01.socal.rr.com [72.129.
22.32]
4 22 ms 15 ms 15 ms 72.129.21.0
5 23 ms 15 ms 39 ms 107.14.19.32
6 14 ms 15 ms 15 ms ae-0-0.pr0.lax10.tbone.rr.com [66.109.6.133]
7 23 ms 24 ms 21 ms 72.14.197.157
8 152 ms 15 ms 15 ms 216.239.46.40
9 15 ms 15 ms 12 ms 72.14.236.13
10 15 ms 15 ms 15 ms lax02s02-in-f7.1e100.net [74.125.224.199]

Trace complete.

C:\Windows\System32>


Phos

@rr.com

I'm having similar problems as of about 1.5 weeks ago. Between 8-11 PM, my pings to game servers and voice servers skyrocket. The weird part is that some servers ping normally, 40-55ms. I'm guessing that one of the main routes is affected on Time Warner's network, while the alternative is not as congested.

I figured customer support wouldn't be much help, so I'm considering switching ISPs. I'm living in the Charlotte, NC area.


ball2hi

join:2012-12-02
Anaheim, CA

I too am considering switching ISPs, but the only other provider in my area is AT&T and I've heard bad reviews of them. Maybe not as bad as TW though...



Trebonious
Premium
join:2001-06-29
Dallas, TX
Reviews:
·Time Warner Cable
reply to ball2hi

Click for full size
Smokeping from California
Click for full size
Smokeping from Kansas

16 month view from California

16 month view from New Jersey
I believe this is an end-route issue since throughput doesn't change but I do feel the same "sluggishness" when visiting certain sites. Especially prevalent when Hurricane Sandy hit. But it was happening well before then as well.

For what it's worth, 1400 mile speed test:


ball2hi

join:2012-12-02
Anaheim, CA

To the above poster.

I'm not sure what to do with this information? If it's an end-route issue, how do I solve it without help from my useless ISP?



Trebonious
Premium
join:2001-06-29
Dallas, TX
Reviews:
·Time Warner Cable
reply to ball2hi

Based on the information provided you will probably want to contact nfoservers.com since it appears to be a peering issue.

That's just a best guess. But your latency jumps after it leaves TWC network.

Savvis for Chicago (Savvis has been known for issues) and Global Crossing for Dallas (yet another big provider with known issues)

Again, take that with a grain of salt. But it's not an issue within TWC network hence the lack of willingness to help fix. NFOServers is the customer that can make the difference since they are peering with those networks to provide their network bandwidth (granted I'm sure it's more like NFOServers is leasing out of another company who is doing the peering).

With issues like this, I would guess if they started working on the issue today (which they are probably already aware of) it would take them a few months, minimum to make any significant progress in relieving the congestion.


ball2hi

join:2012-12-02
Anaheim, CA

What I want to have explained is, how do I have problems to all gameservers (Disregarding host) to Seattle/Chicago/Dallas/Atlanta but my friend who lives 5/10min from me who has TWC and 15DL/1UP doesn't have any of the problems I have.

I'm going to ask her to do a tracert/ping for me later today.


silentjoker

join:2008-09-13
Hermitage, PA

don't to tracert its just for finding hops to a location.

use pathping

this will test packet loss and ping times to each hop.

Also remember this. Even if your friend is next door you guys could be on 2 separate nodes for your internet. I ran into this problem where I live. Im on 1 node and my neighbor is on another node. Its a smoke and mirrors game on the old. Im on TWC internet and I have problems and my friends don't line. There is so much that is different that people don't see or know about. Also remember there is changes going on in twc network daily. I moved across town and has docsis 3 at my old address and new address after install said the node doesn't support it yet and after 2 days of phone calls to special places I wake up and see the docsis streams have been enabled at 5:32 am randomly on a sat morning. So just have faith they have network infrastructure people that do see problems etc and are working on resolving conflicts it just depends on when "management" has funds to say ok lets do this.

but I hope pathping opens your eyes on your problems. Also please google to find how to read the output cause some switch's or routers on hops will read 100% packet loss to them due to no ping response but 100% packets will pass threw to the next hope. That's the 2 numbers it displays. packet loss to the hop and packet loss threw the hop