In the past few weeks I have lost my TiVo connection as COX doesn't support cable cards for those anymore, so I was forced to Contour and Panaramic WiFi. I will miss the TiVo, but the Contour surpris...
Honestly it's more for freedom. Sure I could use ethernet but I'd be stuck in the office. This lets me move about.
I guess you could say I have both. I have three routers (TP-Link Deco) that are in a mesh. Each has four ethernet connections which is handy. The new connection is with a modem they added in the living room. My actual modem is in the office in the back of the house. Again I hear what you're saying, but the interference disappears after a few hours so it has to be something in the area.
I appreciate COX replying though. Maybe something will come from that.
So this morning I was noticing extreme packet loss on my WiFi so I checked my PC directly connected the router and I'm seeing the same packet loss. So of course I bypassed my router and wouldn't you know it? I am experiencing the same packet loss. Go figure. Previously I was posting via my cell, but now I'm on my PC and I've confirmed I'm not getting a NAT'd IP, so this either my modem (it's a COX modem - ARRIS TM3402A 8x32 I believe) or something else is going on. At present I don't have the latency, but here's a brief snippet of what I was seeing this morning and this is AFTER I moved directly to the modem and took my routers out of the mix. Keep in mind I've seen responses of almost 4000ms (4secs) which is always wonderful.
To answer your questions earlier: Yes I can see why you'd think it was my routers and/or WiFi connectivity, but even without WiFi connected I'm seeing the same thing, so clearly something else is happening. I really hope someone from COX actually looks at this, because as far as I'm concerned, as much as it's been happening this is unacceptable and I can barely do my job.
Reply from 8.8.8.8: bytes=32 time=24ms TTL=116 Request timed out. Reply from 8.8.8.8: bytes=32 time=31ms TTL=116 Reply from 8.8.8.8: bytes=32 time=23ms TTL=116 Reply from 8.8.8.8: bytes=32 time=24ms TTL=116 Reply from 8.8.8.8: bytes=32 time=24ms TTL=116 Reply from 8.8.8.8: bytes=32 time=24ms TTL=116 Reply from 8.8.8.8: bytes=32 time=24ms TTL=116 Reply from 8.8.8.8: bytes=32 time=32ms TTL=116 Request timed out. Reply from 8.8.8.8: bytes=32 time=29ms TTL=116 Reply from 8.8.8.8: bytes=32 time=22ms TTL=116 Reply from 8.8.8.8: bytes=32 time=26ms TTL=116 Reply from 8.8.8.8: bytes=32 time=23ms TTL=116 Request timed out. Reply from 8.8.8.8: bytes=32 time=34ms TTL=116 Reply from 8.8.8.8: bytes=32 time=23ms TTL=116 Reply from 8.8.8.8: bytes=32 time=24ms TTL=116 Request timed out. Reply from 8.8.8.8: bytes=32 time=24ms TTL=116 Reply from 8.8.8.8: bytes=32 time=28ms TTL=116 Request timed out. Reply from 8.8.8.8: bytes=32 time=27ms TTL=116 Reply from 8.8.8.8: bytes=32 time=22ms TTL=116 Request timed out. Reply from 8.8.8.8: bytes=32 time=26ms TTL=116 Reply from 8.8.8.8: bytes=32 time=23ms TTL=116 Reply from 8.8.8.8: bytes=32 time=24ms TTL=116 Reply from 8.8.8.8: bytes=32 time=24ms TTL=116 Request timed out. Reply from 8.8.8.8: bytes=32 time=26ms TTL=116 Reply from 8.8.8.8: bytes=32 time=23ms TTL=116 Reply from 8.8.8.8: bytes=32 time=23ms TTL=116 Reply from 8.8.8.8: bytes=32 time=26ms TTL=116 Reply from 8.8.8.8: bytes=32 time=24ms TTL=116 Reply from 8.8.8.8: bytes=32 time=24ms TTL=116 Reply from 8.8.8.8: bytes=32 time=25ms TTL=116 Reply from 8.8.8.8: bytes=32 time=24ms TTL=116 Reply from 8.8.8.8: bytes=32 time=24ms TTL=116 Reply from 8.8.8.8: bytes=32 time=23ms TTL=116 Reply from 8.8.8.8: bytes=32 time=25ms TTL=116 Request timed out. Reply from 8.8.8.8: bytes=32 time=27ms TTL=116 Reply from 8.8.8.8: bytes=32 time=24ms TTL=116 Reply from 8.8.8.8: bytes=32 time=25ms TTL=116 Reply from 8.8.8.8: bytes=32 time=24ms TTL=116 Reply from 8.8.8.8: bytes=32 time=31ms TTL=116 Reply from 8.8.8.8: bytes=32 time=24ms TTL=116 Reply from 8.8.8.8: bytes=32 time=28ms TTL=116 Reply from 8.8.8.8: bytes=32 time=24ms TTL=116 Reply from 8.8.8.8: bytes=32 time=24ms TTL=116 Request timed out. Reply from 8.8.8.8: bytes=32 time=25ms TTL=116
Hello, the purpose of the Cox Internet Forum is to allow customers to discuss technical topics related to residential Cox Cable, Telephone and High-Speed Internet services with other customers. This appears as if you may need for someone to look into your account personally due to the connection issues you have expressed. We can definitely assist you with this. Please reach us on Twitter at CoxHelp, visit us on Facebook, or email by at cox.help@cox.com anytime for assistance. We are always happy to help.
You're welcome, if you have sent an email. It should have been replied to. If some time has lapsed, please send us another one and we will be happy to assist.
so I checked my PC directly connected the router and I'm seeing the same packet loss.
So now you are getting packet loss on wired? Direct to the modem no less. When did this change? I thought you said your wired connections were good. That's what made me think it was a wifi issue.
Try running "tracert 8.8.8.8". That should show you where the packet loss is occuring. If it's the first hop when connected direct to the TM3402, then it's between the modem and Cox and seeing your signal levels will help. If the problem doesn't happen all the time, try using Pingplotter. This shows things like latency spikes and packet loss over time. You can share the data by going to File > Share > Create sharing page. It shouldn't show anything private, but if you are concerned, don't post it here but share it with Cox. That should show them when and where the problem is happening.
I believed it was a WiFi issue, but today I decided to bypass my routers and test it and sure enough, when I see packet loss on COX-WiFi I'm also seeing it on the ARRIS. I have been running a direct ping for a while, but a traceroute is probably a good idea. It seems to be calming down right now, but you can still see a few timeouts here and there.
tracert -d 8.8.8.8
Tracing route to 8.8.8.8 over a maximum of 30 hops
1 8 ms 9 ms 7 ms 10.96.8.1 2 8 ms 8 ms 17 ms 100.127.78.98 3 12 ms 13 ms 20 ms 100.120.100.40 4 * * 25 ms 68.1.1.13 5 * 23 ms 22 ms 72.215.224.173 6 24 ms 22 ms 23 ms 172.253.51.23 7 * * 22 ms 209.85.250.77 8 23 ms 23 ms 23 ms 8.8.8.8
Trace complete.
*************************
I will grab Pingplotter as that's a good idea. I do see quite a few uncorrectables on the ARRIS, so that points to a possible issue and maybe a node split is needed, but just throwing it out there. Here is the screenshot you have requested to give an idea:
I did clear the counters right after taking that and haven't seen any re-occurrences so far. I'm going to grab Pingplotter and try to get more details. It's so intermittent it's hard to determine where the issue is. The SNR looks good, so maybe it's the modem itself? All I can do is replace it and go from there I suppose. I am grateful for your responses though.
Sorry, but I am still not understanding your network. If you are getting internet from the TM3402, why do you have the CGM4141? You should only have 1 device providing internet. You can have 2 devices, one for phone and one for internet, just not 2 devices providing internet. Not sure if relevant to your issue.
Also, CoxWifi isn't your normal wifi connection. It's the hotspot wifi name that is broadcast from gateways like the CGM4141 and also APs out on the pole. You should only connect to CoxWifi when you are away from your house. It is routed differently and is throttled to less then 50Mbps.
As for your signal levels, downstream looks good. I do see some uncorrectables around 117Mhz-147Mhz, but i don't think that is your main problem. What I find more troublesome is your upstream is very low. Should be in the mid to upper 30's at least. 40's is better. Usually the lower the upstream the better, but if you have noise/ingress on your node, a low upstream can cause issues. Do you know how the coax gets from the street to the office? I assume there is a splitter, but how many, what kind, and any amps or filters? If you don't know or can't find out, I suggest working with Colleen. Hopefully she can get to the bottom of it. Good luck!