dhar
join:2004-07-05
Baton Rouge, LA
| [LA] Slow in Baton Rouge 70810
Lately, my HSI has been very sluggish in the evenings. I just pinged the gateway (8:15 PM, 12/11/08), and I've copied the results below. It's not as bad during the day, and it improves late at night. I'm in Baton Rouge, zip code 70810.
Pinging 68.11.159.129 with 32 bytes of data:
Reply from 68.11.159.129: bytes=32 time=448ms TTL=254
Reply from 68.11.159.129: bytes=32 time=243ms TTL=254
Reply from 68.11.159.129: bytes=32 time=96ms TTL=254
Request timed out.
Reply from 68.11.159.129: bytes=32 time=252ms TTL=254
Request timed out.
Reply from 68.11.159.129: bytes=32 time=61ms TTL=254
Reply from 68.11.159.129: bytes=32 time=158ms TTL=254
Reply from 68.11.159.129: bytes=32 time=407ms TTL=254
Reply from 68.11.159.129: bytes=32 time=118ms TTL=254
Reply from 68.11.159.129: bytes=32 time=242ms TTL=254
Reply from 68.11.159.129: bytes=32 time=58ms TTL=254
Reply from 68.11.159.129: bytes=32 time=241ms TTL=254
Reply from 68.11.159.129: bytes=32 time=74ms TTL=254
Reply from 68.11.159.129: bytes=32 time=50ms TTL=254
Reply from 68.11.159.129: bytes=32 time=71ms TTL=254
Reply from 68.11.159.129: bytes=32 time=62ms TTL=254
Reply from 68.11.159.129: bytes=32 time=228ms TTL=254
Reply from 68.11.159.129: bytes=32 time=380ms TTL=254
Reply from 68.11.159.129: bytes=32 time=182ms TTL=254
Reply from 68.11.159.129: bytes=32 time=247ms TTL=254
Reply from 68.11.159.129: bytes=32 time=207ms TTL=254
Reply from 68.11.159.129: bytes=32 time=122ms TTL=254
Reply from 68.11.159.129: bytes=32 time=91ms TTL=254
Reply from 68.11.159.129: bytes=32 time=321ms TTL=254
Reply from 68.11.159.129: bytes=32 time=243ms TTL=254
Reply from 68.11.159.129: bytes=32 time=62ms TTL=254
Reply from 68.11.159.129: bytes=32 time=316ms TTL=254
Reply from 68.11.159.129: bytes=32 time=462ms TTL=254
Reply from 68.11.159.129: bytes=32 time=26ms TTL=254
Reply from 68.11.159.129: bytes=32 time=81ms TTL=254
Reply from 68.11.159.129: bytes=32 time=58ms TTL=254
Reply from 68.11.159.129: bytes=32 time=25ms TTL=254
Reply from 68.11.159.129: bytes=32 time=372ms TTL=254
Reply from 68.11.159.129: bytes=32 time=80ms TTL=254
Reply from 68.11.159.129: bytes=32 time=82ms TTL=254
Reply from 68.11.159.129: bytes=32 time=168ms TTL=254
Reply from 68.11.159.129: bytes=32 time=277ms TTL=254
Reply from 68.11.159.129: bytes=32 time=259ms TTL=254
Reply from 68.11.159.129: bytes=32 time=37ms TTL=254
Reply from 68.11.159.129: bytes=32 time=142ms TTL=254
Reply from 68.11.159.129: bytes=32 time=556ms TTL=254
Request timed out.
Reply from 68.11.159.129: bytes=32 time=104ms TTL=254
Reply from 68.11.159.129: bytes=32 time=159ms TTL=254
Reply from 68.11.159.129: bytes=32 time=120ms TTL=254
Reply from 68.11.159.129: bytes=32 time=199ms TTL=254
Reply from 68.11.159.129: bytes=32 time=32ms TTL=254
Request timed out.
Reply from 68.11.159.129: bytes=32 time=310ms TTL=254
Reply from 68.11.159.129: bytes=32 time=33ms TTL=254
Reply from 68.11.159.129: bytes=32 time=48ms TTL=254
Reply from 68.11.159.129: bytes=32 time=261ms TTL=254
Ping statistics for 68.11.159.129:
Packets: Sent = 53, Received = 49, Lost = 4 (7% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 556ms, Average = 181ms
Control-C |
|
Fubar
join:2001-02-20
Phoenix, AZ | What kind of modem?
Can you get levels from »192.168.100.1
Do you have a router? Have you bypassed it? |
|
dhar
join:2004-07-05
Baton Rouge, LA
| said by Fubar  :What kind of modem? Can you get levels from » 192.168.100.1 Levels were outstanding at the time (S/N=37, Down=-3, Up=39) and don't vary much. I check at least every couple of days. |
|
Fubar
join:2001-02-20
Phoenix, AZ
| reply to Fubar
OK
What does your log show?
said by Fubar :Do you have a router? Have you bypassed it? |
|
CoxTech1
VIP
join:2002-04-25
Chesapeake, VA | reply to dhar
I've asked your local market to look into the connection issues you are experiencing. |
|
brettv04
join:2009-01-21
Baton Rouge, LA | reply to dhar
I am experiencing the exact same problem as you for the past 6 months and I am in 70810 as well. In the evenings I can only get less than 1 MB, but I am paying for 15 MB. Is the node in this area just extremely overloaded? |
|
CoxTech1
VIP
join:2002-04-25
Chesapeake, VA | If you want to PM me the modem's MAC address I can look into this for you. |
|
brettv04
join:2009-01-21
Baton Rouge, LA | reply to dhar
PM sent, let me know what you find. Thanks. |
|
dhar
join:2004-07-05
Baton Rouge, LA
| The problem continues. I'm going to start keeping records of it. Here are today's results:
1/26/2009, 2:01 PM
Ping statistics for 68.11.159.129:
Packets: Sent = 63, Received = 63, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 178ms, Average = 22ms
1/26/2009, 9:04 PM
Ping statistics for 68.11.159.129:
Packets: Sent = 55, Received = 43, Lost = 12 (21% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 541ms, Average = 189ms |
|
CoxTech1
VIP
join:2002-04-25
Chesapeake, VA | If looks like the modem is logging lots of sync timing failures. It might be time to have a technician come out and take a look. |
|
dhar
join:2004-07-05
Baton Rouge, LA
| The following is pretty typical. The Internet is very slow for several hours in the evenings, and it correlates with the slow pings and 20% packet loss to the default gateway observed at these times.
1/28/2009, 2:57 PM
Ping statistics for 68.11.159.129:
Packets: Sent = 151, Received = 151, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 34ms, Average = 12ms
1/28/2009, 7:50 PM
Ping statistics for 68.11.159.129:
Packets: Sent = 158, Received = 158, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 306ms, Average = 57ms
1/28/2009, 8:28 PM
Ping statistics for 68.11.159.129:
Packets: Sent = 68, Received = 55, Lost = 13 (19% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 913ms, Average = 183ms
1/28/2009, 9:40 PM
Ping statistics for 68.11.159.129:
Packets: Sent = 68, Received = 54, Lost = 14 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 536ms, Average = 152ms
1/28/2009, 10:29 PM
Ping statistics for 68.11.159.129:
Packets: Sent = 108, Received = 106, Lost = 2 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 1051ms, Average = 133ms |
|
dhar
join:2004-07-05
Baton Rouge, LA
| Not quite as bad last night, but still very slow performance coinciding with the 9:08 reading:
1/29/2009, 7:56 PM
Ping statistics for 68.11.159.129:
Packets: Sent = 204, Received = 202, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 505ms, Average = 80ms
1/29/2009, 9:08 PM
Ping statistics for 68.11.159.129:
Packets: Sent = 1482, Received = 1243, Lost = 239 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 1197ms, Average = 158ms
1/29/2009, 9:51 PM
Ping statistics for 68.11.159.129:
Packets: Sent = 172, Received = 171, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 499ms, Average = 81ms
1/29/2009, 11:58 PM
Ping statistics for 68.11.159.129:
Packets: Sent = 207, Received = 207, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 26ms, Average = 8ms |
|
brettv04
join:2009-01-21
Baton Rouge, LA
| reply to CoxTech1
Have you heard anything from the local market. It still isn't any better. No errors on modem at all. Get over 20mb in morning and early afternoon. I'm lucky to pull down 300k at night though. I have replaced the modem with a different one as well as connect it to the main cable input to the house and it does the same thing. |
|
tornadog
join:2008-12-02
Baton Rouge, LA
 ·Cox HSI
| I came looking for a solution to this same issue and guess what I am in 70810 too. While the behavior used to happen at night, today the whole day, i was hitting at or below the 2 MBps mark. I am on the premier plan which is at 9 MBps. I tried downloading a file and at the time the browsing got so sluggish, I was getting timeouts. |
|
CoxTech1
VIP
join:2002-04-25
Chesapeake, VA | If you want to PM me the modem's MAC address I can look into this issue for you. |
|
tornadog
join:2008-12-02
Baton Rouge, LA
·Cox HSI
| I talked to Cox online support and they didnt see anything wrong at the modem's end. Anyway, the next day, I checked my speed and it was back to normal. Could have been a glitch in the lines.
Anyone know whats the bandwidth limits of the premier connection. Is it market specific. My preferred connection is supposed to be 10000/800, according to the tech I chatted with. |
|
xxwinmanxx
@cox.net
| reply to dhar
WOW! I thought I was going crazy with these latency issues in 70810. I am having the EXACT same problem as you all are describing. I play WOW and typically my pings are in the 80ms level. Well, these past few months, things have been escalating to horrible pings. I have been putting up with it for a while cause I thought it was my 8 year old surfboard 4200 modem and router. I bought a new SB 5101 and dlink router. The problem was still there. It is like clock work, around 8:30pm latency spikes up to 1600ms and I get disconnected from WOW. Then for the rest of the night I will hover with approx 500ms ping. At around 10:30 ish the system will go back to a reasonable 150 ping.
I dont have any copies of tracerts or pings but if the cox person in here would like that info I can get it next time the issue happens and I dont mind PMing the mac address as well. |
|
tornadog
join:2008-12-02
Baton Rouge, LA
·Cox HSI
| Heres my tracert to google.com, and I am on premier connection!!!!
Tracing route to google.com [209.85.171.100]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms unknown [192.168.1.1]
2 1033 ms 1732 ms 1547 ms 10.130.178.1
3 1574 ms 1458 ms 870 ms 24.248.104.61
4 1154 ms 1047 ms 1202 ms ip24-248-104-182.br.br.cox.net [24.248.104.182]
5 1635 ms 827 ms 831 ms dalsbbrj01-ae0.r2.dl.cox.net [68.1.0.142]
6 705 ms 432 ms 501 ms 66.249.94.94
7 1488 ms 1548 ms 1603 ms 216.239.47.121
8 1916 ms 691 ms 499 ms 209.85.242.21
9 1361 ms 1679 ms 769 ms 216.239.48.50
10 1144 ms 1547 ms 2014 ms 209.85.248.129
11 1209 ms 1592 ms 1044 ms 216.239.46.204
12 752 ms 1125 ms 1426 ms 64.233.174.127
13 893 ms 1578 ms 1741 ms 209.85.251.125
14 1275 ms 1772 ms 1352 ms 74.125.31.134
15 1428 ms 1563 ms 1616 ms cg-in-f100.google.com [209.85.171.100]
Trace complete. |
|
tornadog
join:2008-12-02
Baton Rouge, LA | testing at 7 AM on speakeasy speedtst gave me 16000 down and 2500 up, which seems about right for premier, right?
So its something ahppening at night between 530pm and 10pm every day. |
|
xxwinmanxx
join:2009-02-19
Baton Rouge, LA | Yes, I agree. Although I notice it alot more between 7:30pm and 10pm |
|
