 ellinj0
join:2004-10-10 Danbury, CT
| [RI] Dreadfully Slow
Last couple days my service has been abysmal. Its gotten to the point that using dial up is faster.
Here is some info, any thing stand out before I call cox and complain.
Downstream Frequency 747000000 Hz Signal to Noise Ratio 36 dB QAM QAM256 Network Access Control Object ON Power Level 4 dBmV Upstream Channel ID 3 Frequency 19408000 Hz Ranging Service ID 7964 Symbol Rate 2.560 Msym/s Power Level 47 dBmV
and a ping to cox.com
1 2 ms 1 ms 1 ms 192.168.1.1 2 20 ms 16 ms 6 ms 10.2.80.1 3 8 ms 8 ms 8 ms wwcksysc01-gex0102000.ri.ri.cox.net [68.9.8.97]
4 8 ms 11 ms 9 ms ip68-9-7-1.ri.ri.cox.net [68.9.7.1] 5 13 ms 8 ms 7 ms provdsrj02-ge500.rd.ri.cox.net [68.9.14.105] 6 20 ms 9 ms 11 ms provbbrj01-ge020.rd.ri.cox.net [68.1.0.48] 7 32 ms 19 ms 12 ms provbbrj02-so000.rd.ri.cox.net [68.1.1.173] 8 32 ms 13 ms 14 ms 68.1.0.253 9 33 ms 18 ms 17 ms 68.1.0.250 10 36 ms 26 ms 18 ms mrfdbbrj02-ge030.rd.dc.cox.net [68.1.1.3] 11 33 ms 23 ms 22 ms nrfkbbrj02-so000000.rd.hr.cox.net [68.1.1.235] 12 34 ms 24 ms 23 ms nrfkbbrj01-ge030.rd.hr.cox.net [68.1.0.22] 13 46 ms 61 ms 35 ms dukebbrj01-so000100.rd.at.cox.net [68.1.0.20] 14 47 ms 42 ms 36 ms dukedsrj01-ge610.tc.at.cox.net [68.1.1.121] 15 * * * Request timed out. 16 lkhndsrc01-fe0435.rd.at.cox.net [68.1.1.165] reports: Destination net unre achable. |
|
 ellinj0
join:2004-10-10 Danbury, CT
| still bad tonight. It was working pretty well for a short period of time. Cox claims there is nothing wrong.
Here is a pathping output
Tracing route to www.l.google.com [64.233.161.104] over a maximum of 30 hops: 0 mini-me.ri.cox.net [192.168.1.131] 1 192.168.1.1 2 10.2.80.1 3 wwcksysc01-gex0102000.ri.ri.cox.net [68.9.8.97] 4 * ip68-9-7-1.ri.ri.cox.net [68.9.7.1] 5 provdsrj01-ge600.rd.ri.cox.net [68.9.14.101] 6 provbbrj01-ge020.rd.ri.cox.net [68.1.0.48] 7 * provbbrj02-so000.rd.ri.cox.net [68.1.1.173] 8 68.1.0.253 9 * 68.1.0.250 10 mrfdbbrj02-ge030.rd.dc.cox.net [68.1.1.3] 11 ashbbrj02-so000.r2.as.cox.net [68.1.1.232] 12 68.105.30.118 13 209.85.130.18 14 72.14.236.202 15 * 216.239.48.190 16 od-in-f104.google.com [64.233.161.104]
Computing statistics for 400 seconds...
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 mini-me.ri.cox.net [192.168.1.131]
0/ 100 = 0% | 1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1 0/ 100 = 0% | 2 11ms 2/ 100 = 2% 2/ 100 = 2% 10.2.80.1 0/ 100 = 0% | 3 13ms 2/ 100 = 2% 2/ 100 = 2% wwcksysc01-gex0102000.ri.ri.cox.net [68.9.8.97] 0/ 100 = 0% | 4 12ms 0/ 100 = 0% 0/ 100 = 0% ip68-9-7-1.ri.ri.cox.net [68.9.7.1] 1/ 100 = 1% | 5 13ms 2/ 100 = 2% 1/ 100 = 1% provdsrj01-ge600.rd.ri.cox.net [68.9.14.101] 0/ 100 = 0% | 6 15ms 1/ 100 = 1% 0/ 100 = 0% provbbrj01-ge020.rd.ri.cox.net [68.1.0.48] 4/ 100 = 4% | 7 18ms 5/ 100 = 5% 0/ 100 = 0% provbbrj02-so000.rd.ri.cox.net [68.1.1.173] 1/ 100 = 1% | 8 18ms 6/ 100 = 6% 0/ 100 = 0% 68.1.0.253 2/ 100 = 2% | 9 25ms 12/ 100 = 12% 4/ 100 = 4% 68.1.0.250 0/ 100 = 0% | 10 28ms 14/ 100 = 14% 6/ 100 = 6% mrfdbbrj02-ge030.rd.dc.cox.net [68.1.1.3] 0/ 100 = 0% | 11 26ms 17/ 100 = 17% 9/ 100 = 9% ashbbrj02-so000.r2.as.cox.net [68.1.1.232] 0/ 100 = 0% | 12 --- 100/ 100 =100% 92/ 100 = 92% 68.105.30.118 0/ 100 = 0% | 13 25ms 8/ 100 = 8% 0/ 100 = 0% 209.85.130.18 1/ 100 = 1% | 14 27ms 9/ 100 = 9% 0/ 100 = 0% 72.14.236.202 1/ 100 = 1% | 15 26ms 10/ 100 = 10% 0/ 100 = 0% 216.239.48.190 3/ 100 = 3% | 16 25ms 13/ 100 = 13% 0/ 100 = 0% od-in-f104.google.com [64.233.161.104] |
|
 jamesb478
join:2005-12-29 Foster, RI
·Cox HSI
| reply to ellinj0 I am having the same issues too. I live in Foster, RI and usually get around 2-2.4mB/s up and i am only getting 1mB/s now. Im at my friends house now and he is having the same prob, so it is a network issues, maybe because of the work they are doing on the network this month? |
|
  NoVA_CoxUser Stand back from the cage -- The RF bites Premium join:2004-07-06 Alexandria, VA
·Cox HSI
4 edits | reply to ellinj0 Your traces show that you have come all the way down to NoVA (Merrifield) before going out to Ashburn, VA to peer-out of Cox's network.
Cox's nationwide backbone -- possibly a little out-of-date -- is depicted on page 2 of Cox Optical Internet.
While I'm speculating here ... it might be that you guys are caught-up in the same Merrifield congestion issues affecting us down here every afternoon from about 3:00 or 4:00 PM 'til 1:00 AM.
(Merrifield is the home of mrfdbbrj02-ge030.rd.dc.cox.net [68.1.1.3] from your tracert)
See: »[VA] Fairfax Cox Latency Once Again and »[VA] Northern VA speeds - Major performance issues. |
|
 ellinj0
join:2004-10-10 Danbury, CT
| Things have been better today, interestingly it looks like traffic is not going through merrifield at the moment.
Tracing route to www.l.google.com [64.233.161.99] over a maximum of 30 hops: 0 TP-Ellin.ri.cox.net [192.168.1.105] 1 DD-WRT [192.168.1.1] 2 10.2.80.1 3 wwcksysc01-gex0102000.ri.ri.cox.net [68.9.8.97] 4 ip68-9-7-1.ri.ri.cox.net [68.9.7.1] 5 provdsrj02-ge500.rd.ri.cox.net [68.9.14.105] 6 ashbbrj02-so000.r2.as.cox.net [68.1.1.232] 7 68.105.30.118 8 209.85.130.16 9 64.233.175.169 10 216.239.48.190 11 od-in-f99.google.com [64.233.161.99] |
|