dslreports logo
 
    All Forums Hot Topics Gallery
spc

spacer

Search Topic:
uniqs
1986
share rss forum feed

zoomie09

join:2010-01-16
Bossier City, LA

Bad latency/packet loss

Been having bad latency and packet loss for the past month. Two weeks ago a tech come check my lines and he said everything was fine, and also that others in my area have been experiencing similar issues. He said he would call me when they found the issue, but that never happened. Chatted with a tech support agent recently and still no word about what is going on. Heres a tracert from last night:

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

1 42 ms 17 ms 79 ms 10.238.0.1
2 106 ms 13 ms 9 ms 173-219-234-48-link.sta.suddenlink.net [173.219.
234.48]
3 213 ms 197 ms 267 ms cdm-66-76-31-41.lfkn.suddenlink.net [66.76.31.41
]
4 387 ms 81 ms 19 ms cdm-66-76-30-133.tylrtx.suddenlink.net [66.76.30
.133]
5 80 ms 50 ms 24 ms ###-###-##4-169-link.tex.sta.suddenlink.net [173
.219.254.169]
6 113 ms 72 ms 24 ms 72.14.223.10
7 142 ms 106 ms 178 ms 72.14.233.85
8 103 ms

and one from tonight:

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

1 73 ms 104 ms 83 ms 10.238.0.1
2 211 ms 45 ms * link.sta.suddenlink.net [173.219.234.48]
3 202 ms * 43 ms cdm-66-76-31-41.lfkn.suddenlink.net
4 307 ms * 157 ms 133.tylrtx.suddenlink.net [66.76.30.133]
5 407 ms 59 ms 206 ms link.tex.sta.suddenlink.net [173
.219.254.169]
6 95 ms * * 72.14.223.10
7 71 ms * 213 ms 72.14.233.77
8 98 ms 172 ms 156 ms 209.85.240.91
9 206 ms * * dfw06s16-in-f9.1e100.net [74.125.227.105]
10 89 ms 46 ms 197 ms dfw06s16-in-f9.1e100.net [74.125.227.105]

Please let me know if there is anything else i can do to help get this fixed.

zoomie09

join:2010-01-16
Bossier City, LA
Update from this morning. My latency seems fine right now, im guessing thats because the network isnt busy right now. Does this mean the node in my area is overloaded during peak hours in the evening? Heres the tracert from this morning:

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

C:\Users\Dallas>tracert google.com

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

1 6 ms 7 ms 8 ms 10.238.0.1
2 23 ms 7 ms 6 ms 173-219-234-46-link.sta.suddenlink.net [173.219.
234.46]
3 50 ms 10 ms 11 ms cdm-66-76-31-44.lfkn.suddenlink.net [66.76.31.44
]
4 10 ms 10 ms 14 ms 173-219-246-184-link.sta.suddenlink.net [173.219
.246.184]
5 41 ms 98 ms 40 ms 173-219-254-169-link.tex.sta.suddenlink.net [173
.219.254.169]
6 48 ms 44 ms 48 ms 72.14.223.10
7 38 ms 38 ms 37 ms 72.14.233.77
8 37 ms 37 ms 37 ms 209.85.240.91
9 324 ms 34 ms 35 ms dfw06s16-in-f7.1e100.net [74.125.227.103]

Trace complete.

zoomie09

join:2010-01-16
Bossier City, LA
Just tried playing an online game and still got latency issues... I did a ping and here are the results:

Packets: Sent - 50, Received = 50, Lost = 0 (0% loss)
Approximate round trip time in milli-seconds:
Minimum = 35 ms, Maximum = 865ms, Average = 101ms

About 1 out of 10 pings would hit the 800ms mark out of the 50 pings i sent out.


moldypickle
Premium
join:2009-01-04
Haughton, LA
kudos:3
Reviews:
·Suddenlink
I'm in the Bossier area and run off that main hub. My trace to the same IP are showing fine for me.

I'm also going to add now that your first hop is taking a SEVERE beating. You're showing 104ms to your modem. It should be under 10ms or you are having a problem on your computer.

You need to double check that you have no programs running that are using your bandwidth. Also check for spyware/adware/viruses.

But when you are pinging terribly to your modem, the connection can only get worse past that point. Need to find what is causing that
--
20/2 Suddenlink : Current
5/1 CMA : Old
15/2 TWC : Old


Gaff
Just like the gypsy woman said

join:1999-09-05
North TX, US
reply to zoomie09
In addition, you should do a test at »www.pingtest.net and see what that says.
--
My PC Gaming Blog
»www.gaffonline.com

zoomie09

join:2010-01-16
Bossier City, LA
Well I am away from my house for the weekend and I just tested my computer's connection and everything is running flawlessly at this location (about 4 hours away). No latency issues or packet loss. I scanned my computer and there is no spyware viruses etc... So the only thing I can think is that it is my modem or the suddenlink network. The tech that came out said my modem was fine so not sure what to think at this point.


moldypickle
Premium
join:2009-01-04
Haughton, LA
kudos:3
I can PROMISE you that when your first hop to the modem is high ping, you have an issue within your house. SL network starts at hop 2

zoomie09

join:2010-01-16
Bossier City, LA
I will try buying a new modem and see if that solves it.


moldypickle
Premium
join:2009-01-04
Haughton, LA
kudos:3
Reviews:
·Suddenlink
are you able to slap up a screenshot of your signal stats too?

The modem very well could be starting to go bad on you, but from my experience it's more often a router overloading (doesn't look like you have one) or it's a program the user doesn't even realize he has running.

Also, I'm not seeing the packet loss that you mentioned in the title of the post.

Are you using a laptop and wirelessly connecting to a modem/router combo unit?
--
20/2 Suddenlink : Current
5/1 CMA : Old
15/2 TWC : Old

zoomie09

join:2010-01-16
Bossier City, LA
I normally use a wireless router, but ive been connecting straight to the modem since ive been experiencing the issues and it hasn't been making any difference.

Here's the modem signal stats

Downstream Bonding Channel Value
Channel ID 38 37 39 40
Frequency 579000000 Hz 573000000 Hz 585000000 Hz 591000000 Hz
Signal to Noise Ratio 35 dB 35 dB 36 dB 35 dB
Downstream Modulation QAM256 QAM256 QAM256 QAM256
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
-2 dBmV -2 dBmV -2 dBmV -2 dBmV
Upstream Bonding Channel Value
Channel ID 3
Frequency 32000000 Hz
Ranging Service ID 5821
Symbol Rate 5.120 Msym/sec
Power Level 43 dBmV
Upstream Modulation [3] 16QAM
[3] 64QAM

Ranging Status Success
Signal Stats (Codewords) Bonding Channel Value
Channel ID 38 37 39 40
Total Unerrored Codewords 10239876711 1649941978 1649941985 1649943293
Total Correctable Codewords 1278 1272 1159 1116
Total Uncorrectable Codewords 2591 2460 2648 1461

zoomie09

join:2010-01-16
Bossier City, LA
Got back into town tonight and tried out the connection and not getting any latency problems. I'll see what happens over the next few days, hopefully its back for good!


moldypickle
Premium
join:2009-01-04
Haughton, LA
kudos:3
Your signal looks fine. When you are having troubles just give it a check real quick. Atleast to rule it out.

zoomie09

join:2010-01-16
Bossier City, LA

3 edits
So ive been testing my connection at different times of the day and the latency issues only appear in the evenings from about 4-10PM. Any other time of day my latency and ping times are good. Here's a snapshot of a ping command to the 2nd hop (i think its my modem's internal or CMTS ip?) that any traceroute goes outside my home during these bad hours:

C:\Users\Dallas>ping -n 20 10.238.0.1

Pinging 10.238.0.1 with 32 bytes of data:
Reply from 10.238.0.1: bytes=32 time=34ms TTL=255
Reply from 10.238.0.1: bytes=32 time=18ms TTL=255
Reply from 10.238.0.1: bytes=32 time=134ms TTL=255
Reply from 10.238.0.1: bytes=32 time=172ms TTL=255
Reply from 10.238.0.1: bytes=32 time=241ms TTL=255
Reply from 10.238.0.1: bytes=32 time=102ms TTL=255
Request timed out.
Reply from 10.238.0.1: bytes=32 time=108ms TTL=255
Request timed out.
Request timed out.
Reply from 10.238.0.1: bytes=32 time=16ms TTL=255
Reply from 10.238.0.1: bytes=32 time=213ms TTL=255
Reply from 10.238.0.1: bytes=32 time=36ms TTL=255
Reply from 10.238.0.1: bytes=32 time=59ms TTL=255
Request timed out.
Reply from 10.238.0.1: bytes=32 time=257ms TTL=255
Reply from 10.238.0.1: bytes=32 time=107ms TTL=255
Reply from 10.238.0.1: bytes=32 time=211ms TTL=255
Reply from 10.238.0.1: bytes=32 time=12ms TTL=255
Reply from 10.238.0.1: bytes=32 time=125ms TTL=255

Ping statistics for 10.238.0.1:
Packets: Sent = 20, Received = 16, Lost = 4 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 257ms, Average = 115ms

here is the ping response from my cable modem during the same time frame:

C:\Users\Dallas>ping -n 40 192.168.100.1

Pinging 192.168.100.1 with 32 bytes of data:
Reply from 192.168.100.1: bytes=32 time=2ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64
Reply from 192.168.100.1: bytes=32 time1ms TTL=64

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

So, I feel like peak hours are causing latency issues. I'll take another ping snapshot when the connection is normal again. Also, my SB6120 modem's firmware says it is 1.0.1.8 from Apr of 2009, that seems kinda old...

Your Thoughts?


moldypickle
Premium
join:2009-01-04
Haughton, LA
kudos:3
Reviews:
·Suddenlink
your second ping is to the private side of your modem, you never leave your network. 10.238.0.1 from the best i can tell is at or before the cmts, which would mean the issue is either your modem is having troubles, or your node is saturated. If you have a rented modem, you could see about an exchange.

Could you run a smokeping for a few days and post the results. That'll give you viewable intervals around the clock and a better idea of what your connection is doing. Alternately, you could join the group line monitor for free. It'll ping your modem once every 5 minutes I believe and will give you a VERY good record to use.
--
20/2 Suddenlink : Current
5/1 CMA : Old
15/2 TWC : Old

zoomie09

join:2010-01-16
Bossier City, LA
Ok I will do that, its 7 AM and my connection is fine again. Here's a traceroure and ping:

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

C:\Users\Dallas>tracert google.com

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

1 9 ms 13 ms 9 ms 10.238.0.1
2 9 ms 12 ms 14 ms 173-219-234-48-link.sta.suddenlink.net [173.219.
234.48]
3 16 ms 11 ms 17 ms cdm-66-76-31-41.lfkn.suddenlink.net [66.76.31.41
]
4 19 ms 15 ms 14 ms cdm-66-76-30-133.tylrtx.suddenlink.net [66.76.30
.133]
5 16 ms 17 ms 15 ms 173-219-254-169-link.tex.sta.suddenlink.net [173
.219.254.169]
6 20 ms 18 ms 15 ms 72.14.223.10
7 15 ms 27 ms 19 ms 72.14.233.85
8 36 ms 16 ms 16 ms 216.239.43.187
9 25 ms 13 ms 15 ms dfw06s17-in-f1.1e100.net [74.125.227.129]

Trace complete.

C:\Users\Dallas>ping -n 40 10.238.0.1

Pinging 10.238.0.1 with 32 bytes of data:
Reply from 10.238.0.1: bytes=32 time=17ms TTL=255
Reply from 10.238.0.1: bytes=32 time=8ms TTL=255
Reply from 10.238.0.1: bytes=32 time=8ms TTL=255
Reply from 10.238.0.1: bytes=32 time=7ms TTL=255
Reply from 10.238.0.1: bytes=32 time=8ms TTL=255
Reply from 10.238.0.1: bytes=32 time=10ms TTL=255
Reply from 10.238.0.1: bytes=32 time=8ms TTL=255
Reply from 10.238.0.1: bytes=32 time=15ms TTL=255
Reply from 10.238.0.1: bytes=32 time=27ms TTL=255
Reply from 10.238.0.1: bytes=32 time=8ms TTL=255
Reply from 10.238.0.1: bytes=32 time=8ms TTL=255
Reply from 10.238.0.1: bytes=32 time=15ms TTL=255
Reply from 10.238.0.1: bytes=32 time=9ms TTL=255
Reply from 10.238.0.1: bytes=32 time=13ms TTL=255
Reply from 10.238.0.1: bytes=32 time=10ms TTL=255
Reply from 10.238.0.1: bytes=32 time=14ms TTL=255
Reply from 10.238.0.1: bytes=32 time=9ms TTL=255
Reply from 10.238.0.1: bytes=32 time=7ms TTL=255
Reply from 10.238.0.1: bytes=32 time=12ms TTL=255
Reply from 10.238.0.1: bytes=32 time=15ms TTL=255
Reply from 10.238.0.1: bytes=32 time=8ms TTL=255
Reply from 10.238.0.1: bytes=32 time=10ms TTL=255
Reply from 10.238.0.1: bytes=32 time=7ms TTL=255
Reply from 10.238.0.1: bytes=32 time=10ms TTL=255
Reply from 10.238.0.1: bytes=32 time=6ms TTL=255
Reply from 10.238.0.1: bytes=32 time=12ms TTL=255
Reply from 10.238.0.1: bytes=32 time=11ms TTL=255
Reply from 10.238.0.1: bytes=32 time=33ms TTL=255
Reply from 10.238.0.1: bytes=32 time=16ms TTL=255
Reply from 10.238.0.1: bytes=32 time=18ms TTL=255
Reply from 10.238.0.1: bytes=32 time=8ms TTL=255
Reply from 10.238.0.1: bytes=32 time=10ms TTL=255
Reply from 10.238.0.1: bytes=32 time=7ms TTL=255
Reply from 10.238.0.1: bytes=32 time=7ms TTL=255
Reply from 10.238.0.1: bytes=32 time=23ms TTL=255
Reply from 10.238.0.1: bytes=32 time=8ms TTL=255
Reply from 10.238.0.1: bytes=32 time=10ms TTL=255
Reply from 10.238.0.1: bytes=32 time=10ms TTL=255
Reply from 10.238.0.1: bytes=32 time=9ms TTL=255
Reply from 10.238.0.1: bytes=32 time=8ms TTL=255

Ping statistics for 10.238.0.1:
Packets: Sent = 40, Received = 40, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 33ms, Average = 11ms

C:\Users\Dallas>

zoomie09

join:2010-01-16
Bossier City, LA
Good news, a few days ago 3 suddenlink trucks showed up to my neighborhood with large spools of cable and were working all day on something. Not sure what they did but whatever they did seems to have fixed all the latency issues!


moldypickle
Premium
join:2009-01-04
Haughton, LA
kudos:3
Reviews:
·Suddenlink
Looking over your troubles, they could have been replacing a main line or adding another link for your node/splitting it.

Glad you're up and running again!

Curiosity, had you been running that smokeping?
--
30/2 Suddenlink : Current
5/1 CMA : Old
15/2 TWC : Old


vector4

@budgetprepay.com
reply to zoomie09
I also am having back latency with Suddenlink out in my area in Haughton. I get ok throughput but I can barely play online games the latency is so bad. These are my pingtest.net results.

»www.pingtest.net/result/72596321 ··· 6321.png

That is at 10am on a Tuesday.


moldypickle
Premium
join:2009-01-04
Haughton, LA
kudos:3
Need a bit more info on this. Post up a signal stats page for us from the modem. And can you start a smokeping for a couple days from the tools menu here on the site.


vector4

@budgetprepay.com
»/r3/smokeping. ··· 730727ff

Thats's my smokeping for the past 12 hours... I thought I set it to run 24 hours but it only ran 12 for some reason. My main problem is in the afternoon which is when I try to play online games when the horrible ping times are prevalent.

I will try ot restart smokeping so it will capture what its like during the main afternoon hours.

You can see from just that 12 hour span that until midnight ping is garbage then gets ok in the early morning hours.

I am having problems getting my PC to connect to the modem without a router, I don't think the modem likes my gigabit NIC or something. I am going to try another PC and attempt to get a router status page.


moldypickle
Premium
join:2009-01-04
Haughton, LA
kudos:3
You'd have to power cycle the modem when you switch NICs, that should release the MAC ID. Atleast here it doesn't seem to kick you off when you change it.

But um, yeah, you are def having some huge packet lose issues there.