san diego

5 Topics

Interesting, odd, and extremely annoying pattern specific internet slow down occurring at 6/7pm every day [San Diego]
PSA: I understand how to code in 4 different programming languages and understand networking at a high level. Cheesy to write this, but refrain from providing basic, simpleton-user information. I for one would like to say I haven't had much issues with cox in the last 3 years. Now, ever since the insane lightning storm in San Diego on Oct. 4 my internet has been severely slowing to an unusable level oddly enough at 6pm every single day. Mind you, I have top of the line equipment I spend hundreds on, all the way down to CAT8 cables. Now, I did diagnosing of all the components of my network and saw that all pieces of equipment functioned. What it is is the service itself is oddly enough throttling to very slow speeds at 6pm. I say this as the tech support mentioned to me to replace the modem to test the connection, and I obliged. Even before getting the modem, I knew my top of the line Motorola was not the problem because funnily enough the issue is stuck to an odd pattern. Today, I got the cox authorized PW7 which features a docsis 3.1 modem and router. Not going to lie, the speeds were amazing on it after I hooked it up and tested at 1pm[remember this time]. Sure enough, even with the new modem, the insane slow down occurred. Now, a tech has been specifically appointed to come at 7pm to catch this weird slow down. Pattern: 10am- 6/7 pm the internet is as perfect as you can get. I have gigblast and get 5 ping 950 down and 37 up. Then, sure enough, as 6/7pm rolls around, the download is cut in half and the upload is decreased from 37 to literally .9 mbps. You can even tell during the day as the websites and other services load instantly and then after 6pm I can't even load a website or do anything. TLDR:Subscriber's equipment is not at fault, even used cox's new modem to test, and a pattern specific slow down of the internet has been occurring at 6pm every single day since Oct. 4th. The level of degradation: download cut by 2/3s and the upload cut from 37 to literally .9 mbps. This all amounts to an unusable connection. If the new cox modem was affected too, we can deduce the old modem was never the problem and the true issue is intermittent occurring at 6pm on. I already have spoken to a supervisor of which has made sure to send a tech at 7pm, which should be a late enough time for the issue to be visible. I am merely writing this to reach out to all and share what an interesting and funny problem this is. Also, I have a weeks worth of speedtests documenting the odd degradation pattern. I also would like to have the first tech visit a day ago waived as this is truly an external problem. I find it laughable when the field techs use their devices before 6pm, of which is when perfect speeds do occur, and claim nothing to be the problem when you describe the complexity of the issue occurring past 6pm. One word: intermittent. I will upload an update on Wed. after the tech shows at 7pm to see what might be the issue. Also, I might be reaching but this issue was only noticeable after the lightning storm in San Diego on Oct. 4th. A literal lightning bolt hit 10 ft from my apartment and rattled everything; I wonder if this has anything to do with this odd issue. Also, for the last 3 years no slowdown has ever occurred, even during peak usage times of 7-11 pm.
Solved
RomanPat
4 years ago Place Internet
2.7KViews
0likes
9Comments
Lots of Jitter, Tons of Packet Loss
Hey there! I have been having severe packet loss and lag in games lately and noticed my ping spiking quite a bit. I contacted Cox, and I was told everything looked fine on my end and the node in my neighborhood was overloaded because of COVID. I had a tech come out about a month ago and he reiterated the overloaded node issue and installed an attenuator on our line. I followed up with COX about a week ago and they sent out a supervisor who just knocked on the door, said the same thing about the overloaded node, and left. Didn't make any changes or attempt to do any diagnostics. They said they split my node on Friday, but I am still seeing a lot of issues. I just ran some of my own diagnostics and found some interesting info. I ran pingplotter and MTR on Google and EAs servers (I mostly play Apex Legends). I discussed the results with some more technical friends who believe it might not just be a local issue but rather peering congestion between COX and Zayo. Please see the images below. https://ibb.co/ThD2R7Z https://ibb.co/ysC10pt https://ibb.co/BsY2G3Z https://ibb.co/8BH34rC We have Gigablast and have just upgraded both our modem and router. I am kind of lost with what to do currently. I have seen people file FCC complaints with some success. But certain applications are just unusable with the jitter and packet loss I am getting. Thank you!
corb3421
4 years ago Place Internet
2.4KViews
0likes
7Comments
5th Technician/Cant fix packet loss
Hello all! I live in San Diego California, 91950 Specifically. For about 3 months now I have not been able to play any games on my PC due to packet loss. Ive had 4 technicians come to my house and say that there is packet loss coming from the tap and that eveyrthing in my home is working as intended. Its been a constant battle with Customer Service trying to explain my issue. With most of them saying that my 50mbps speed is the problem and that I need to updgrade. When I know that clearly isnt the case. my ping is great and I have no latency issues other than packet loss. Here are multiple pings a made at different times of day. C:\Users\josht>ping youtube.com -n 25 Pinging youtube.com [172.217.6.46] with 32 bytes of data: Reply from 172.217.6.46: bytes=32 time=152ms TTL=117 Reply from 172.217.6.46: bytes=32 time=75ms TTL=117 Reply from 172.217.6.46: bytes=32 time=93ms TTL=117 Reply from 172.217.6.46: bytes=32 time=120ms TTL=117 Reply from 172.217.6.46: bytes=32 time=21ms TTL=117 Reply from 172.217.6.46: bytes=32 time=63ms TTL=117 Reply from 172.217.6.46: bytes=32 time=81ms TTL=117 Reply from 172.217.6.46: bytes=32 time=41ms TTL=117 Reply from 172.217.6.46: bytes=32 time=111ms TTL=117 Reply from 172.217.6.46: bytes=32 time=36ms TTL=117 Reply from 172.217.6.46: bytes=32 time=197ms TTL=117 Reply from 172.217.6.46: bytes=32 time=72ms TTL=117 Reply from 172.217.6.46: bytes=32 time=56ms TTL=117 Request timed out. Reply from 172.217.6.46: bytes=32 time=101ms TTL=117 Reply from 172.217.6.46: bytes=32 time=101ms TTL=117 Reply from 172.217.6.46: bytes=32 time=26ms TTL=117 Reply from 172.217.6.46: bytes=32 time=40ms TTL=117 Reply from 172.217.6.46: bytes=32 time=75ms TTL=117 Reply from 172.217.6.46: bytes=32 time=49ms TTL=117 Reply from 172.217.6.46: bytes=32 time=28ms TTL=117 Reply from 172.217.6.46: bytes=32 time=225ms TTL=117 Reply from 172.217.6.46: bytes=32 time=34ms TTL=117 Reply from 172.217.6.46: bytes=32 time=35ms TTL=117 Reply from 172.217.6.46: bytes=32 time=28ms TTL=117 Ping statistics for 172.217.6.46: Packets: Sent = 25, Received = 24, Lost = 1 (4% loss), Approximate round trip times in milli-seconds: Minimum = 21ms, Maximum = 225ms, Average = 77ms C:\Users\josht>ping ea.com -n 25 Pinging ea.com [104.86.72.27] with 32 bytes of data: Reply from 104.86.72.27: bytes=32 time=23ms TTL=59 Reply from 104.86.72.27: bytes=32 time=31ms TTL=59 Reply from 104.86.72.27: bytes=32 time=85ms TTL=59 Reply from 104.86.72.27: bytes=32 time=46ms TTL=59 Reply from 104.86.72.27: bytes=32 time=86ms TTL=59 Reply from 104.86.72.27: bytes=32 time=80ms TTL=59 Reply from 104.86.72.27: bytes=32 time=90ms TTL=59 Reply from 104.86.72.27: bytes=32 time=42ms TTL=59 Reply from 104.86.72.27: bytes=32 time=43ms TTL=59 Reply from 104.86.72.27: bytes=32 time=55ms TTL=59 Reply from 104.86.72.27: bytes=32 time=37ms TTL=59 Reply from 104.86.72.27: bytes=32 time=15ms TTL=59 Reply from 104.86.72.27: bytes=32 time=188ms TTL=59 Reply from 104.86.72.27: bytes=32 time=53ms TTL=59 Reply from 104.86.72.27: bytes=32 time=40ms TTL=59 Reply from 104.86.72.27: bytes=32 time=16ms TTL=59 Request timed out. Reply from 104.86.72.27: bytes=32 time=37ms TTL=59 Reply from 104.86.72.27: bytes=32 time=77ms TTL=59 Reply from 104.86.72.27: bytes=32 time=16ms TTL=59 Reply from 104.86.72.27: bytes=32 time=28ms TTL=59 Reply from 104.86.72.27: bytes=32 time=27ms TTL=59 Reply from 104.86.72.27: bytes=32 time=135ms TTL=59 Reply from 104.86.72.27: bytes=32 time=17ms TTL=59 Reply from 104.86.72.27: bytes=32 time=59ms TTL=59 Ping statistics for 104.86.72.27: Packets: Sent = 25, Received = 24, Lost = 1 (4% loss), Approximate round trip times in milli-seconds: Minimum = 15ms, Maximum = 188ms, Average = 55ms C:\Users\josht>ping youtube.com -n 25 Pinging youtube.com [216.58.194.174] with 32 bytes of data: Reply from 216.58.194.174: bytes=32 time=50ms TTL=118 Reply from 216.58.194.174: bytes=32 time=262ms TTL=118 Reply from 216.58.194.174: bytes=32 time=91ms TTL=118 Reply from 216.58.194.174: bytes=32 time=18ms TTL=118 Reply from 216.58.194.174: bytes=32 time=32ms TTL=118 Reply from 216.58.194.174: bytes=32 time=28ms TTL=118 Request timed out. Reply from 216.58.194.174: bytes=32 time=34ms TTL=118 Reply from 216.58.194.174: bytes=32 time=44ms TTL=118 Reply from 216.58.194.174: bytes=32 time=61ms TTL=118 Request timed out. Reply from 216.58.194.174: bytes=32 time=120ms TTL=118 Reply from 216.58.194.174: bytes=32 time=80ms TTL=118 Reply from 216.58.194.174: bytes=32 time=153ms TTL=118 Reply from 216.58.194.174: bytes=32 time=112ms TTL=118 Reply from 216.58.194.174: bytes=32 time=120ms TTL=118 Reply from 216.58.194.174: bytes=32 time=79ms TTL=118 Reply from 216.58.194.174: bytes=32 time=71ms TTL=118 Reply from 216.58.194.174: bytes=32 time=36ms TTL=118 Reply from 216.58.194.174: bytes=32 time=55ms TTL=118 Reply from 216.58.194.174: bytes=32 time=85ms TTL=118 Reply from 216.58.194.174: bytes=32 time=24ms TTL=118 Reply from 216.58.194.174: bytes=32 time=80ms TTL=118 Reply from 216.58.194.174: bytes=32 time=197ms TTL=118 Reply from 216.58.194.174: bytes=32 time=65ms TTL=118 Ping statistics for 216.58.194.174: Packets: Sent = 25, Received = 23, Lost = 2 (8% loss), Approximate round trip times in milli-seconds: Minimum = 18ms, Maximum = 262ms, Average = 82ms C:\Users\josht>ping google.com =n 25 Bad parameter =n. C:\Users\josht>ping google.com -n 25 Pinging google.com [216.58.195.78] with 32 bytes of data: Request timed out. Reply from 216.58.195.78: bytes=32 time=43ms TTL=118 Request timed out. Reply from 216.58.195.78: bytes=32 time=28ms TTL=118 Reply from 216.58.195.78: bytes=32 time=46ms TTL=118 Reply from 216.58.195.78: bytes=32 time=271ms TTL=118 Reply from 216.58.195.78: bytes=32 time=36ms TTL=118 Reply from 216.58.195.78: bytes=32 time=40ms TTL=118 Reply from 216.58.195.78: bytes=32 time=237ms TTL=118 Reply from 216.58.195.78: bytes=32 time=39ms TTL=118 Reply from 216.58.195.78: bytes=32 time=215ms TTL=118 Reply from 216.58.195.78: bytes=32 time=106ms TTL=118 Reply from 216.58.195.78: bytes=32 time=235ms TTL=118 Reply from 216.58.195.78: bytes=32 time=42ms TTL=118 Request timed out. Reply from 216.58.195.78: bytes=32 time=72ms TTL=118 Request timed out. Reply from 216.58.195.78: bytes=32 time=71ms TTL=118 Request timed out. Reply from 216.58.195.78: bytes=32 time=128ms TTL=118 Request timed out. Reply from 216.58.195.78: bytes=32 time=159ms TTL=118 Request timed out. Reply from 216.58.195.78: bytes=32 time=41ms TTL=118 Reply from 216.58.195.78: bytes=32 time=54ms TTL=118 Ping statistics for 216.58.195.78: Packets: Sent = 25, Received = 18, Lost = 7 (28% loss), Approximate round trip times in milli-seconds: Minimum = 28ms, Maximum = 271ms, Average = 103ms C:\Users\josht>ping amazon.com -n 25 Pinging amazon.com [205.251.242.103] with 32 bytes of data: Reply from 205.251.242.103: bytes=32 time=93ms TTL=239 Reply from 205.251.242.103: bytes=32 time=117ms TTL=239 Reply from 205.251.242.103: bytes=32 time=132ms TTL=239 Reply from 205.251.242.103: bytes=32 time=78ms TTL=239 Reply from 205.251.242.103: bytes=32 time=80ms TTL=239 Reply from 205.251.242.103: bytes=32 time=148ms TTL=239 Request timed out. Reply from 205.251.242.103: bytes=32 time=250ms TTL=239 Reply from 205.251.242.103: bytes=32 time=84ms TTL=239 Reply from 205.251.242.103: bytes=32 time=199ms TTL=239 Reply from 205.251.242.103: bytes=32 time=118ms TTL=239 Reply from 205.251.242.103: bytes=32 time=127ms TTL=239 Reply from 205.251.242.103: bytes=32 time=171ms TTL=239 Reply from 205.251.242.103: bytes=32 time=91ms TTL=239 Reply from 205.251.242.103: bytes=32 time=180ms TTL=239 Reply from 205.251.242.103: bytes=32 time=122ms TTL=239 Reply from 205.251.242.103: bytes=32 time=100ms TTL=239 Reply from 205.251.242.103: bytes=32 time=316ms TTL=239 Reply from 205.251.242.103: bytes=32 time=143ms TTL=239 Reply from 205.251.242.103: bytes=32 time=98ms TTL=239 Reply from 205.251.242.103: bytes=32 time=323ms TTL=239 Reply from 205.251.242.103: bytes=32 time=259ms TTL=239 Reply from 205.251.242.103: bytes=32 time=123ms TTL=239 Reply from 205.251.242.103: bytes=32 time=100ms TTL=239 Reply from 205.251.242.103: bytes=32 time=115ms TTL=239 Ping statistics for 205.251.242.103: Packets: Sent = 25, Received = 24, Lost = 1 (4% loss), Approximate round trip times in milli-seconds: Minimum = 78ms, Maximum = 323ms, Average = 148ms C:\Users\josht>ping cox.com -n 25 Pinging cox.com [45.60.49.167] with 32 bytes of data: Reply from 45.60.49.167: bytes=32 time=61ms TTL=57 Reply from 45.60.49.167: bytes=32 time=29ms TTL=57 Reply from 45.60.49.167: bytes=32 time=38ms TTL=57 Reply from 45.60.49.167: bytes=32 time=17ms TTL=57 Reply from 45.60.49.167: bytes=32 time=54ms TTL=57 Reply from 45.60.49.167: bytes=32 time=143ms TTL=57 Reply from 45.60.49.167: bytes=32 time=21ms TTL=57 Reply from 45.60.49.167: bytes=32 time=102ms TTL=57 Reply from 45.60.49.167: bytes=32 time=44ms TTL=57 Reply from 45.60.49.167: bytes=32 time=17ms TTL=57 Reply from 45.60.49.167: bytes=32 time=129ms TTL=57 Reply from 45.60.49.167: bytes=32 time=15ms TTL=57 Reply from 45.60.49.167: bytes=32 time=31ms TTL=57 Reply from 45.60.49.167: bytes=32 time=46ms TTL=57 Reply from 45.60.49.167: bytes=32 time=13ms TTL=57 Reply from 45.60.49.167: bytes=32 time=191ms TTL=57 Reply from 45.60.49.167: bytes=32 time=61ms TTL=57 Reply from 45.60.49.167: bytes=32 time=22ms TTL=57 Request timed out. Reply from 45.60.49.167: bytes=32 time=154ms TTL=57 Reply from 45.60.49.167: bytes=32 time=49ms TTL=57 Reply from 45.60.49.167: bytes=32 time=209ms TTL=57 Reply from 45.60.49.167: bytes=32 time=117ms TTL=57 Reply from 45.60.49.167: bytes=32 time=47ms TTL=57 Reply from 45.60.49.167: bytes=32 time=70ms TTL=57 Ping statistics for 45.60.49.167: Packets: Sent = 25, Received = 24, Lost = 1 (4% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 209ms, Average = 70ms My issue is not with a specific game. As you can see regular websites have PL Here is a list of things ive done or Ive been told a technician has done *reset modem *disconnect modem from power for 5 minutes and reconnect *swapped out to a new modem *Swapped out to a new ethernet cable *PC is connected directly via Ethernet to modem *technicians "checked" wiring from TAP to modem and state eveything is fine and they would send another tech that works on the street box or poles? *Street tech said that its due to covid and all the kids are jumping online for their classes however I still get packet loss in the middle of the night, early morning etc 24/7 *replaced modem AGAIN to have CS tell me they dont see any packet loss on their end however Im still getting packet loss or "jitter" with cox.com/speedtest and command prompt ping test. Im having a 5th tech come tomorrow morning and I swear Im at a loss I dont know what to do. CS tells me I must upgrade however I doubt that will fix my packet loss. I will just have a greater DL/UL speeds but still have % packet loss.
ArisenPick
5 years ago Place Internet
1.3KViews
0likes
2Comments
Cox IPv6 San Diego
Does Cox have IPv6 rolled out in San Diego?Running https://test-ipv6.com/ on Firefox and Chrome shows No IPv6 address detected. Changed Firefox "network.dns.disableIPv6". value to "True" and can't find a way to set Chrome forIPv6 It does sayyour browser has a real working IPv6 address. The question i have has Cox rolled out IPv6, and if so,how can I get Firefox and Chrome to useIPv6. Running Cox preferred150Mbps/ 10Mbps,ARRIS / Surfboard TM3402 DOCSIS 3.1 32x8, Asus RT-AC86U.
coxcommy
6 years ago Place Internet
2.6KViews
1like
1Comment
Cox Internet Reliability in 92115 has been Poor - What's the fix?
The internet at my home in San Diego has been pathetic lately. I call and I'm told - "yep, you're down". If Cox isn't going to upgrade or fix it, I can't see how we can continue.
MarkinSD
7 years ago Place Internet
798Views
0likes
1Comment