dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1378
share rss forum feed


Loser

join:2000-08-06
Poway, CA

[CA] High latency in the San Diego area

I live around the San Diego (Poway) area and I have the Cox Ultimate Package and everything has been working fine for the past few months. For the past week the latency has been very bad at night. The speed test (from speedtest.net) shows about 50 ms ping and 64 Mbps for download, but always seem to timeout when trying to run the upload (usually see about 6 Mbps). Web pages take about 5-10 seconds to load and sometime won't finish loading the entire page. When playing games, my ping jumps from 80ms to over 1000ms sometimes. The game will be fine for about 10 seconds or so, then I get a lag spike for about 10 seconds. It pretty much repeats that way, sometimes it's fine for a whole 20-30 seconds then lags again. This happens around 7pm to midnight. Everything is working fine again right around midnight so it's making me think it's congestion. I'm unable to confirm if it's happening earlier in the day because I'm not at home and just turn off the modem during that time.

Using a Cisco DPC 3010 and the status page for downstream shows

Channel 1: 0.8 dBmV 41.5 dB
Channel 2: 0.5 dBmV 41.2 dB
Channel 3: 0.5 dBmV 39.7 dB
Channel 4: 0.8 dBmV 41.6 dB
Channel 5: -3.2 dBmV 40.6 dB
Channel 6: -3.4 dBmV 40.1 dB
Channel 7: -3.6 dBmV 38.5 dB
Channel 8: -3.6 dBmV 40.4 dB


lilstone87

join:2009-04-09
Portsmouth, VA
kudos:3
Reviews:
·Cox HSI

I suggest start running some traceroutes during the evenings when this problem is occurring, as its possible routing going bad somewhere. I am also sure one of the tech on here wouldn't mind taking a look at your modem from there end. But they will need your modem's mac address, which that is info you should send threw a PM.



Diego318

@cox.net

Im having the same issues in san diego at night. About every 5 mins i get extreme latency. Ive narrowed it down to this router paltbprj02-ae0.0.rd.pt.cox.net (68.1.0.235). here's what happens:

64 bytes from 68.1.0.235: icmp_req=249 ttl=59 time=92.5 ms
64 bytes from 68.1.0.235: icmp_req=250 ttl=59 time=47.0 ms
64 bytes from 68.1.0.235: icmp_req=251 ttl=59 time=44.7 ms
64 bytes from 68.1.0.235: icmp_req=252 ttl=59 time=44.3 ms
64 bytes from 68.1.0.235: icmp_req=253 ttl=59 time=45.5 ms
64 bytes from 68.1.0.235: icmp_req=254 ttl=59 time=35.1 ms
64 bytes from 68.1.0.235: icmp_req=255 ttl=59 time=47.0 ms
64 bytes from 68.1.0.235: icmp_req=256 ttl=59 time=37.2 ms
64 bytes from 68.1.0.235: icmp_req=257 ttl=59 time=77.6 ms
64 bytes from 68.1.0.235: icmp_req=258 ttl=59 time=137 ms --- starts here
64 bytes from 68.1.0.235: icmp_req=259 ttl=59 time=139 ms
64 bytes from 68.1.0.235: icmp_req=260 ttl=59 time=164 ms
64 bytes from 68.1.0.235: icmp_req=261 ttl=59 time=198 ms
64 bytes from 68.1.0.235: icmp_req=262 ttl=59 time=278 ms
64 bytes from 68.1.0.235: icmp_req=263 ttl=59 time=397 ms
64 bytes from 68.1.0.235: icmp_req=264 ttl=59 time=503 ms
64 bytes from 68.1.0.235: icmp_req=265 ttl=59 time=725 ms
64 bytes from 68.1.0.235: icmp_req=266 ttl=59 time=947 ms
64 bytes from 68.1.0.235: icmp_req=267 ttl=59 time=932 ms
64 bytes from 68.1.0.235: icmp_req=268 ttl=59 time=665 ms
64 bytes from 68.1.0.235: icmp_req=269 ttl=59 time=839 ms
64 bytes from 68.1.0.235: icmp_req=270 ttl=59 time=912 ms
64 bytes from 68.1.0.235: icmp_req=271 ttl=59 time=867 ms
64 bytes from 68.1.0.235: icmp_req=272 ttl=59 time=667 ms
64 bytes from 68.1.0.235: icmp_req=273 ttl=59 time=731 ms
64 bytes from 68.1.0.235: icmp_req=274 ttl=59 time=582 ms --- ends here
64 bytes from 68.1.0.235: icmp_req=275 ttl=59 time=44.3 ms
64 bytes from 68.1.0.235: icmp_req=276 ttl=59 time=45.7 ms
64 bytes from 68.1.0.235: icmp_req=277 ttl=59 time=44.9 ms
64 bytes from 68.1.0.235: icmp_req=278 ttl=59 time=46.8 ms
64 bytes from 68.1.0.235: icmp_req=279 ttl=59 time=34.9 ms
64 bytes from 68.1.0.235: icmp_req=280 ttl=59 time=38.9 ms
64 bytes from 68.1.0.235: icmp_req=281 ttl=59 time=35.3 ms
64 bytes from 68.1.0.235: icmp_req=282 ttl=59 time=31.9 ms
64 bytes from 68.1.0.235: icmp_req=283 ttl=59 time=36.4 ms

this makes online gaming impossible.



Diego318

@cox.net

How are we going to get cox to fix this..? this is going on a week now!

tim@tims-comp:~$ ping 4.2.2.2
PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data.
64 bytes from 4.2.2.2: icmp_req=1 ttl=56 time=760 ms
64 bytes from 4.2.2.2: icmp_req=2 ttl=56 time=747 ms
64 bytes from 4.2.2.2: icmp_req=3 ttl=56 time=896 ms
64 bytes from 4.2.2.2: icmp_req=4 ttl=56 time=607 ms
64 bytes from 4.2.2.2: icmp_req=5 ttl=56 time=34.2 ms
64 bytes from 4.2.2.2: icmp_req=6 ttl=56 time=41.6 ms
64 bytes from 4.2.2.2: icmp_req=7 ttl=56 time=34.8 ms
64 bytes from 4.2.2.2: icmp_req=8 ttl=56 time=36.7 ms
64 bytes from 4.2.2.2: icmp_req=9 ttl=56 time=36.8 ms
64 bytes from 4.2.2.2: icmp_req=10 ttl=56 time=38.7 ms
64 bytes from 4.2.2.2: icmp_req=11 ttl=56 time=35.2 ms
64 bytes from 4.2.2.2: icmp_req=12 ttl=56 time=42.7 ms
64 bytes from 4.2.2.2: icmp_req=13 ttl=56 time=35.1 ms
64 bytes from 4.2.2.2: icmp_req=14 ttl=56 time=35.3 ms
64 bytes from 4.2.2.2: icmp_req=15 ttl=56 time=35.0 ms
64 bytes from 4.2.2.2: icmp_req=16 ttl=56 time=35.5 ms
64 bytes from 4.2.2.2: icmp_req=17 ttl=56 time=35.4 ms
64 bytes from 4.2.2.2: icmp_req=19 ttl=56 time=703 ms
64 bytes from 4.2.2.2: icmp_req=20 ttl=56 time=724 ms
64 bytes from 4.2.2.2: icmp_req=21 ttl=56 time=878 ms
64 bytes from 4.2.2.2: icmp_req=22 ttl=56 time=906 ms
64 bytes from 4.2.2.2: icmp_req=23 ttl=56 time=335 ms
64 bytes from 4.2.2.2: icmp_req=24 ttl=56 time=34.2 ms
64 bytes from 4.2.2.2: icmp_req=25 ttl=56 time=33.8 ms
64 bytes from 4.2.2.2: icmp_req=26 ttl=56 time=46.0 ms
64 bytes from 4.2.2.2: icmp_req=27 ttl=56 time=35.7 ms
64 bytes from 4.2.2.2: icmp_req=28 ttl=56 time=34.7 ms
64 bytes from 4.2.2.2: icmp_req=29 ttl=56 time=37.9 ms
64 bytes from 4.2.2.2: icmp_req=30 ttl=56 time=39.1 ms
64 bytes from 4.2.2.2: icmp_req=31 ttl=56 time=49.6 ms
64 bytes from 4.2.2.2: icmp_req=32 ttl=56 time=48.7 ms
64 bytes from 4.2.2.2: icmp_req=33 ttl=56 time=34.9 ms
64 bytes from 4.2.2.2: icmp_req=34 ttl=56 time=41.1 ms
64 bytes from 4.2.2.2: icmp_req=35 ttl=56 time=242 ms
64 bytes from 4.2.2.2: icmp_req=36 ttl=56 time=515 ms
64 bytes from 4.2.2.2: icmp_req=37 ttl=56 time=549 ms
64 bytes from 4.2.2.2: icmp_req=38 ttl=56 time=590 ms
64 bytes from 4.2.2.2: icmp_req=39 ttl=56 time=603 ms
64 bytes from 4.2.2.2: icmp_req=40 ttl=56 time=606 ms
64 bytes from 4.2.2.2: icmp_req=41 ttl=56 time=36.2 ms
64 bytes from 4.2.2.2: icmp_req=42 ttl=56 time=37.8 ms
64 bytes from 4.2.2.2: icmp_req=43 ttl=56 time=36.6 ms
64 bytes from 4.2.2.2: icmp_req=44 ttl=56 time=37.5 ms
64 bytes from 4.2.2.2: icmp_req=45 ttl=56 time=46.8 ms
64 bytes from 4.2.2.2: icmp_req=46 ttl=56 time=35.2 ms
64 bytes from 4.2.2.2: icmp_req=47 ttl=56 time=38.8 ms
64 bytes from 4.2.2.2: icmp_req=48 ttl=56 time=47.9 ms
64 bytes from 4.2.2.2: icmp_req=49 ttl=56 time=40.7 ms
64 bytes from 4.2.2.2: icmp_req=50 ttl=56 time=40.9 ms
64 bytes from 4.2.2.2: icmp_req=51 ttl=56 time=37.0 ms
64 bytes from 4.2.2.2: icmp_req=52 ttl=56 time=35.0 ms
64 bytes from 4.2.2.2: icmp_req=53 ttl=56 time=68.4 ms
64 bytes from 4.2.2.2: icmp_req=54 ttl=56 time=37.1 ms
64 bytes from 4.2.2.2: icmp_req=55 ttl=56 time=786 ms
64 bytes from 4.2.2.2: icmp_req=56 ttl=56 time=901 ms
64 bytes from 4.2.2.2: icmp_req=57 ttl=56 time=695 ms
64 bytes from 4.2.2.2: icmp_req=58 ttl=56 time=436 ms
64 bytes from 4.2.2.2: icmp_req=59 ttl=56 time=288 ms
64 bytes from 4.2.2.2: icmp_req=60 ttl=56 time=523 ms
64 bytes from 4.2.2.2: icmp_req=61 ttl=56 time=36.1 ms
64 bytes from 4.2.2.2: icmp_req=62 ttl=56 time=36.7 ms
64 bytes from 4.2.2.2: icmp_req=63 ttl=56 time=40.0 ms
64 bytes from 4.2.2.2: icmp_req=64 ttl=56 time=37.1 ms
64 bytes from 4.2.2.2: icmp_req=65 ttl=56 time=35.5 ms
64 bytes from 4.2.2.2: icmp_req=66 ttl=56 time=36.4 ms
64 bytes from 4.2.2.2: icmp_req=67 ttl=56 time=39.9 ms
64 bytes from 4.2.2.2: icmp_req=68 ttl=56 time=36.5 ms
64 bytes from 4.2.2.2: icmp_req=69 ttl=56 time=48.5 ms
64 bytes from 4.2.2.2: icmp_req=70 ttl=56 time=36.0 ms
64 bytes from 4.2.2.2: icmp_req=71 ttl=56 time=34.6 ms
64 bytes from 4.2.2.2: icmp_req=72 ttl=56 time=806 ms
^C
--- 4.2.2.2 ping statistics ---
73 packets transmitted, 71 received, 2% packet loss, time 72096ms
rtt min/avg/max/mdev = 33.806/225.542/906.007/298.328 ms
tim@tims-comp:~$



SDman2012

@cox.net

I also live in San Diego (La Mesa area), for the last couple of weeks even during the day time, I've experienced high latency and packet loss. Whats the deal here? At night, its even worse. (Packet loss is at 19% on a 100 ping count, and latency is up in the 100s to www.google.com, when usually its 10-20ms)


Diego318

join:2012-11-02
La Mesa, CA

SDman2012,

Yes, Im in La Mesa too!

Im on spring st. where are you?