ContributionsMost RecentMost LikesSolutionsRe: Constant packet loss for multiple years. Multiple tech visits have not helped, given up on calling. Just curious if you were able to try this. Any luck or still same issue? Re: Constant packet loss for multiple years. Multiple tech visits have not helped, given up on calling. It looks like your modem has the defective puma 6 chip: https://approvedmodemlist.com/intel-puma-6-modem-list-chipset-defects/ Buy something without the defective Intel chip from Amazon. If that doesn't resolve the issue you can easily return it. I have to have a voice plan so Cox forces me to use the TM3402 which has this defective chip. So I had to buy my own modem and use a splitter, it really **. Re: higher pings when gaming I don't think it's normal to have pings such as this to a CMTS: Pinging 10.48.64.1 with 32 bytes of data: Reply from 10.48.64.1: bytes=32 time=8ms TTL=254 Reply from 10.48.64.1: bytes=32 time=11ms TTL=254 Reply from 10.48.64.1: bytes=32 time=8ms TTL=254 Reply from 10.48.64.1: bytes=32 time=27ms TTL=254 Reply from 10.48.64.1: bytes=32 time=7ms TTL=254 Reply from 10.48.64.1: bytes=32 time=10ms TTL=254 Reply from 10.48.64.1: bytes=32 time=8ms TTL=254 Reply from 10.48.64.1: bytes=32 time=15ms TTL=254 Reply from 10.48.64.1: bytes=32 time=18ms TTL=254 Reply from 10.48.64.1: bytes=32 time=8ms TTL=254 Reply from 10.48.64.1: bytes=32 time=8ms TTL=254 Reply from 10.48.64.1: bytes=32 time=20ms TTL=254 Reply from 10.48.64.1: bytes=32 time=14ms TTL=254 Reply from 10.48.64.1: bytes=32 time=11ms TTL=254 Reply from 10.48.64.1: bytes=32 time=30ms TTL=254 Reply from 10.48.64.1: bytes=32 time=11ms TTL=254 Reply from 10.48.64.1: bytes=32 time=21ms TTL=254 Reply from 10.48.64.1: bytes=32 time=12ms TTL=254 Reply from 10.48.64.1: bytes=32 time=8ms TTL=254 Reply from 10.48.64.1: bytes=32 time=11ms TTL=254 Reply from 10.48.64.1: bytes=32 time=18ms TTL=254 Reply from 10.48.64.1: bytes=32 time=7ms TTL=254 Request timed out. Reply from 10.48.64.1: bytes=32 time=7ms TTL=254 Reply from 10.48.64.1: bytes=32 time=25ms TTL=254 Reply from 10.48.64.1: bytes=32 time=7ms TTL=254 Reply from 10.48.64.1: bytes=32 time=9ms TTL=254 Reply from 10.48.64.1: bytes=32 time=18ms TTL=254 Reply from 10.48.64.1: bytes=32 time=22ms TTL=254 Reply from 10.48.64.1: bytes=32 time=8ms TTL=254 Reply from 10.48.64.1: bytes=32 time=34ms TTL=254 Reply from 10.48.64.1: bytes=32 time=9ms TTL=254 Reply from 10.48.64.1: bytes=32 time=6ms TTL=254 Reply from 10.48.64.1: bytes=32 time=21ms TTL=254 Reply from 10.48.64.1: bytes=32 time=7ms TTL=254 Reply from 10.48.64.1: bytes=32 time=5ms TTL=254 Reply from 10.48.64.1: bytes=32 time=13ms TTL=254 Reply from 10.48.64.1: bytes=32 time=9ms TTL=254 Reply from 10.48.64.1: bytes=32 time=56ms TTL=254 Reply from 10.48.64.1: bytes=32 time=9ms TTL=254 Reply from 10.48.64.1: bytes=32 time=17ms TTL=254 Reply from 10.48.64.1: bytes=32 time=10ms TTL=254 Reply from 10.48.64.1: bytes=32 time=55ms TTL=254 Reply from 10.48.64.1: bytes=32 time=7ms TTL=254 Can someone please confirm my neighborhood line is working right? Either that or I still have signal issues and spikes like this make playing games unbearable 😞 Re: higher pings when gaming Also if the problem is not with Cox is there anyone I can contact to help me? Also is it normal for me to hit Los Angeles first before going East? higher pings when gaming Can someone please explain to me why I'm pinging 90-115 to Chicago servers from Arizona? It shouldn't be that high when it used to be in the 60s consistently. It's very depressing to see someone connect from Scotland and play in the same server with sometimes lower ping. Don't even ask about NY servers, I might as well be playing internationally with the pings I get there. I have a traceroute below. Is there anything I can do? It's really affecting my experience when other players are hitting 30-60 from all over the country. I'm plugged into the router directly (even tried directly to the modem as well) and besides this issue everything else is working really well now. Tracing route to 97-66-128-38.clients.gthost.com [38.128.66.97] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.0.1 2 9 ms 8 ms 6 ms 10.48.64.1 3 19 ms 20 ms 31 ms 100.127.74.52 4 37 ms 36 ms 49 ms 100.120.100.12 5 10 ms 10 ms 13 ms lag-103.bear2.phoenix1.level3.net [4.14.52.225] 6 * * * Request timed out. 7 42 ms 45 ms 41 ms gtt-level3-2x10g.losangels.level3.net [4.68.62.2] 8 80 ms 80 ms 83 ms xe-5-1-3.cr2-chi1.ip4.gtt.net [89.149.142.53] 9 81 ms 80 ms 80 ms ip4.gtt.net [69.174.9.238] 10 95 ms 79 ms 78 ms 97-66-128-38.clients.gthost.com [38.128.66.97] Trace complete.