Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
New Contributor
•
Horrible slow downs at night with Ultimate Tier
Hey everyone, hoping to get some help here since Cox hasn't been able to fix my issue. To start off I have the Ultimate package and I get the advertised speeds in the morning and afternoon, just this morning I did a speed test and got a whopping 171 Mbps down. At night it's a whole different story, I'm barely getting 7 Mbps down and sometimes its way worse than that. Cox support has been trying to solve this issue for the past six months to no avail. I have the Cisco DCP3010 modem and I also have a Netgear Nighthawk AC router. My two PCs are running on internal N wireless cards, with one of them no more than 15 feet from the router (this is the PC that got 171 Mbps down in the morning). I know that the advertised speeds aren't guaranteed for wireless set ups but in my case if I'm able to get those sort of speeds during the day and not at night, then the issue isn't with my equipment (correct me if I'm wrong though). Before I wrote this, I did a speed test and I barely got 5 Mbps down. I live in a brand new home in a fairly new neighborhood and I'm just baffled with what's going on with my speeds. I have a friend who also lives on another new development and he was getting 70 Mbps down at the same time I did my test tonight. I would greatly appreciate any feedback and what I can do to resolve my issue. I will also provide the readings for my modem.
| Power Level: | Signal to Noise Ratio: | |
| Channel 1: | -1.8 dBmV | 37.9 dB |
| Channel 2: | 0.7 dBmV | 39.8 dB |
| Channel 3: | 1.6 dBmV | 40.0 dB |
| Channel 4: | 2.5 dBmV | 40.3 dB |
| Channel 5: | -0.9 dBmV | 39.4 dB |
| Channel 6: | -1.2 dBmV | 39.1 dB |
| Channel 7: | -1.7 dBmV | 38.6 dB |
| Channel 8: | -1.7 dBmV | 38.9 dB |
| Power Level: | |
| Channel 1: | 49.2 dBmV |
| Channel 2: | 46.9 dBmV |
| Channel 3: | 47.9 dBmV |
| Channel 4: | 50.9 dBmV |
Jrod0125
New Contributor
•
Any takers?
0
0
Health_Edge
+5 more
Valued Contributor III
•
When the speed slows down, have you tried bypassing t he router and going direct? Could be something on your network is eating up bandwidth or something else.
0
0
Area51
New Contributor
•
A little logical troubleshooting is in order. You'll need to connect a pc to one of the lan ports on the router and disable it's wifi adapter so you will definitely be using the lan port.
When your wifi speed drops at night run the speed test on the wired machine and compare the two. If the wired speed is low also then it points to the isp system. If the wired speed is high and your wifi low then it is a wifi problem on your end.
The two most common issues are interference from another system that may only be active at night or, someone else has connected to your wifi and stealing bandwith. Every tablet, phone, laptop, or other pc connected to the wifi will reduce your available bandwidth.
Look at the wireless connections in the router to get an idea of how many units are connected to it.
Identify each of the mac addresses and record them for later use by turning the wifi or the unit off and see which client goes away. Any mac address you can't identify could be a bandwidth pirate.
Get a wifi scanner app for your phone and see if there is another system interfering with you.
You should be using wpa2 aes security on your routers wifi radios to help keep the pirates out. If you do have security running change the password (something long and garbled) and see if it helps.
Good luck
0
0
Jrod0125
New Contributor
•
Already done that several times. I've gone through 3 modems and 3 routers to try and solve the issue. Created new networks with new passwords and on one of my PCs, I get the same speed results whether it's wired or wireless.
0
0
Health_Edge
+5 more
Valued Contributor III
•
Wired to what though? The router or the modem? But that atleast rules out wireless signal issues. And if it happens with multiple routers and modems, its probably not related to that. Sounds like something on your network is using a bunch of bandwidth at a certian time. What router do you have currently? There might be a way to check. Or you could check by turning off PC's one by one when its slow, and see when it becomes fast again.
0
0
Jrod0125
New Contributor
•
I bought a 50 ft Cat 6 cable that I ran from my modem straight to my PC and I got the same speeds wired as I did when I tested wireless ( 24 Mbps down). I have a Netgear Nighthawk router which from all the reviews I've read, it's supposed to be one of the fastest out there.
0
0
Health_Edge
+5 more
Valued Contributor III
•
Yea, don't think I can help with this one. Good luck though. Maybe someone else from the forum can try.
0
0
Jrod0125
New Contributor
•
My slow down issue continues. I did two tests tonight on a wired connection (modem to pc) and I'm getting between 3 and 15 Mbps down. It seems like no matter what tier I have, I'm always going to have this issue. Anyone have ideas on what it could be?
0
0
Health_Edge
+5 more
Valued Contributor III
•
I will bite, simply because before I just thought you werent bypassing your router. A couple things
1. What is the connection rate between modem and PC? Windows Key + R > NCPA.CPL > Right click local area connection and left click status.
2. What are you using to test your speed. Perhaps the test site itself s having problems. If its speed.net try Visualware Speedtest, or Cox Speedtest under Internet Tools on Cox.net
3.Do you see real life examples of the slow speed? IE Does youtube stream fast in HD?
4. Try running a tracert to look for latency and post the results. Windows Key + R > CMD > Tracert cox.net
0
0
Jrod0125
New Contributor
•
Connection rate between my PC and modem is 1.0 Gbps. Here is the tracert. I did the cox speed test after and it shows 4.28 Mbps down and 43.67 Mbps up. It is very noticeable in real life and it's quite annoying to be paying for the Ultimate tier and not getting the performance that Cox advertises. Thanks for trying to help though, I really appreciate it. Also, this only happens at night, say between 6 PM and midnight.
Tracing route to google.com [74.125.239.2]
over a maximum of 30 hops:
1 16 ms 12 ms 11 ms 10.0.16.1
2 15 ms 13 ms 14 ms 172.22.60.230
3 16 ms 15 ms 16 ms 172.22.60.230
4 16 ms 16 ms 17 ms 68.10.8.225
5 17 ms 17 ms 17 ms 68.1.4.139
6 21 ms 22 ms 22 ms ip70-167-150-18.at.at.cox.net [70.167.150.18]
7 34 ms 19 ms 18 ms 216.239.46.250
8 24 ms 19 ms 21 ms 72.14.236.146
9 29 ms 28 ms 33 ms 66.249.95.231
10 35 ms 34 ms 34 ms 72.14.239.66
11 94 ms 86 ms 86 ms 72.14.239.83
12 94 ms 86 ms 96 ms 64.233.174.191
13 90 ms 89 ms 89 ms 216.239.43.148
14 87 ms 87 ms 87 ms lax04s09-in-f2.1e100.net [74.125.239.2]
Trace complete.
0
0
Health_Edge
+5 more
Valued Contributor III
•
The fact that your first hop is at least 11ms is not normal. Can you try this when the problem is occurring?
Ping -n 50 192.168.100.1
Latency to the modem should be less then 1ms to 1ms max. If its more, you either have a connection problem between modem and PC, or a modem issue. If latency is good to modem, but not good to first hop, then the problem is something between modem and first hop. Here is my tracert (with router hooked up) for comparsion.
Tracing route to lax04s09-in-f2.1e100.net [74.125.239.2]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 6 ms 10.2.x.x <--- This is your first hop.
3 6 ms 7 ms 7 ms 68.9.8.73
4 8 ms 10 ms 8 ms ip98-190-33-152.ri.ri.cox.net [98.190.33.152]
5 15 ms 13 ms 13 ms 68.1.5.157
6 14 ms 13 ms 13 ms 68.105.31.87
7 18 ms 13 ms 15 ms 209.85.255.68
8 14 ms 13 ms 13 ms 72.14.236.208
9 43 ms 32 ms 31 ms 216.239.46.217
10 53 ms 42 ms 44 ms 209.85.248.214
11 83 ms 56 ms 55 ms 216.239.46.52
12 84 ms 82 ms 81 ms 216.239.46.153
13 81 ms 81 ms 82 ms 64.233.174.191
14 82 ms 81 ms 81 ms 216.239.43.148
15 81 ms 81 ms 82 ms lax04s09-in-f2.1e100.net [74.125.239.2]
Trace complete.
0
0
Jrod0125
New Contributor
•
This is what I got. I did another tracert by the way and the first hop was 9ms this time around.
Pinging 192.168.100.1 with 32 bytes of data:
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.100.1:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
0
0
Health_Edge
+5 more
Valued Contributor III
•
I don't know then. Were talking maybe 6ms higher then normal. Maybe thats normal for your area. I live in RI, a very small state, so maybe the infrastructure is closer. But that brings us back to square one. WHen the problem occurs, can you try different tests: Even something as simple as trying to watch a youtube video in HD. The data so far just isn't so anything drastically wrong, with the exception of somewhat high Upstream power level and slightly high latency on the first hop intermittently. Nothing that I would say is capable of causing 10x drop in speed. Anyone else have any iideas? I would say its almost ready for a technician to confirm with a tester or laptop from outside, to at least isolate the problem.
0
0
smtips
New Contributor II
•
Welcome to the club. Now go and read this article, and make sure you keep good notes on everyone you talk to, everything they promise and everything they do. Make sure to ask for appropriate credits when they get it corrected, and hopefully it won't take as much hoop-jumping as I had to do with them.
http://forums.cox.com/forum_home/internet_forum/f/5/p/5697/22175.aspx
0
0