Shotbot
join:2002-01-25
Baton Rouge, LA
| What is Cox doing?
What is Cox doing right now? I've read all the posts that deal with tech support. I've read some of the posts that deal with the speeds and packet loss. I just want to know, in plain english, what the hell Cox engineers are doing with the network? It's been awhile since the transition so there should be some changes. I've also noticed that some @home servers are still online. Does this mean Cox is still using the @home network? If so, why? If I have overlooked a post or any info, please inform me. I guess I'm just frustrated with the service. I mean, what if the service stays this way? Will you switch? Decisions,decisions.... |
|
toy4x4
join:2001-06-26
Jenks, OK
| I have no idea. I am moving in probably 9 months to a new house. I hope to have a choice between Cable and DSL. I prefer to stay with cable, but won't put up with the crappy network.
[text was edited by author 2002-03-07 18:07:37] |
|
PapaSmurf
A Smurfy Salute
VIP
join:2001-08-05
smurfville | Toy,
Where are you tracing/pinging too, and do you know what devices are giving the loss? Also curious, what tool did you use to run the graph? |
|
imtim83
You All Deserve The Economic Meltdown
Premium
join:2001-06-03
Kenner, LA
| reply to Shotbot
That is the line status test from dslreports that you can do from this site. Here is mine which is really strange looking and i have no idea why.
Here is my latest line quality test too! It sure is a roller coaster ride my line qaulity test thats all i have to say.
»/quality/nil/693188 |
|
toy4x4
join:2001-06-26
Jenks, OK
| reply to PapaSmurf
PapaSmurf,
That chart is the results of the 24x7 line monitoring tool here on DSLReports (»/schedule).
As for Packet loss, here is a line test from yesterday:
»/quality/nil/692161
Packet loss is on the Cox network. Not that I give Cox slack when it's level3 losing them. They picked level3 and it's their responsibility to drive the issues with them too.
Still waiting for todays to complete which means it's dropping packets right now. Always takes awhile when losing packets. I'll post that one soon. |
|
toy4x4
join:2001-06-26
Jenks, OK | reply to Shotbot
And here is todays.
»/quality/nil/693262 |
|
coxunhappy
join:2002-02-26
Glastonbury, CT | reply to Shotbot
I am asking the same question - are they doing anything about this???? Is anything changing - improving - being fixed??? |
|
meester
Premium
join:2000-06-03
Oklahoma City, OK
clubs:
| reply to imtim83
forget It.....
[text was edited by author 2002-03-07 23:20:57] |
|
Shotbot
join:2002-01-25
Baton Rouge, LA |  reply to Shotbot
I feel like an ant and Cox is pest control |
|
cwren
join:2001-01-03
Oklahoma City, OK |  reply to Shotbot
I'll probably give them a few more months, but if I don't see any progress by then, I'm switching to DSL. |
|
imtim83
You All Deserve The Economic Meltdown
Premium
join:2001-06-03
Kenner, LA | reply to Shotbot
Thank goodness bellsouth is rated really well on the isp rating chart. Not #1 but its rated pretty good if you ask me. |
|
chrisf8657
join:2002-01-27
Glendale, AZ
clubs: 
| reply to Shotbot
I think I remember someone posting a picture of the dummies book...Networking for dummies - and said cox should read it. Maybe they should still 
LOLOLOLOL
--
Chris
Windows NT LAN Engineer and Lead Developer, www.lcompmicro.com |
|
2kmaro
Think
Premium,ExMod 1 BC
join:2000-07-11
ColossalCave
clubs:
| reply to imtim83
Perhaps it's time for you to sign up with BellSouth, dump Cox and let us know how things are with them? Might relieve some of the misery you seem to be in? You're lucky in that you have the option - some don't. Try it, you might like it??
--
I am not now, nor have I ever been, a member of the Comcast Party. |
|
toy4x4
join:2001-06-26
Jenks, OK | reply to Shotbot
I'm thinking about going back to dialup cause this is so rediculous. |
|
BillRoland
Premium
join:2001-01-21
Ocala, FL
clubs: | reply to 2kmaro
Thanks for saying what we're all thinking 2k...I appreciate it... |
|
coxengr
Premium,VIP
join:2002-03-09
Atlanta, GA
| reply to Shotbot
Speaking for Cox, please understand that Ping is going to yield highly variable and often inaccurate results. See my separate post on DNS - pinging the DNS server is not going to yield anything useful in regards to how well the DNS server is operating.
Since Ping is using ICMP, and since ICMP is the lowest priority and is often just dropped by the routers, it's not an accurate tool for packet loss. Yes, ping is great for quick and dirty tests, and to verify connectivity. But it has its limits.
To make matters worse, we are currently experiencing a problem with our metro router vendor and behavior with Ping. We are seeing ping packets get dropped, even though cpu util is less than 20% on the boxes. We have a ticket open with the vendor, but have not received feedback on when to expect a fix.
Lastly, apologies that no device names are appearing when performing traceroutes on the Cox backbone. We had to turn up the network in such a hurry, this is one of the small cleanup items that we need to circle back around on. We're working to get those entries put in.
Hope this info helps. |
|
ip_vic
join:2002-02-18
Boston, MA
| said by coxengr:
Since Ping is using ICMP, and since ICMP is the lowest priority and is often just dropped by the routers, it's not an accurate tool for packet loss. Yes, ping is great for quick and dirty tests, and to verify connectivity. But it has its limits.
Hope this info helps.
Good point! Also, people should know that when a router responds to ICMP, often they must process the packets in their route processors or on their routing engines. The routers running backbone circuits have distributed processing and often the packets that you send _through_ the router to your destination are not processed up in the route processor. Instead each line card has a copy of the routing table and does it's own lookup and forward process. This is the difference between what's called the 'control plane' and the 'data plane'. Pinging the final destination is a bit more useful for end to end packet loss tests since you run through the data plane on all routers in the path.
You may find situations where if you ping a router interface, you'll see loss but ping something on the other side of that router, the loss is better.
regards
-V |
|
2kmaro
Think
Premium,ExMod 1 BC
join:2000-07-11
ColossalCave
clubs:
| reply to coxengr
First - Welcome to DSLReports (or more accurately, Broadband Reports). It is good to see someone visiting us finally who does actually "speak for Cox". Now, if anyone gives you any unreasonable flack, simply ignore it and perhaps use the little "hey mod" link within a post info area to call attention to it. While I'm not even real happy with the service I'm getting, I don't think jumping down the throat of a potential source of help is a really smart move to make. I've seen what happens to techs and mgt types in other forums where there are problems of this nature.
Next - The bottom line argument for everyone here is going to be this, plain and simple: Everything was working just fine and dandy before transition from Cox@Home to CoxHSI.
Take my own personal experience: Pre transition speeds were in neighborhood of 2200/250, and generally they're holding up to that for me now. However, pre transition pings were always STEADY and packet loss was non-existent.
Since transition we are seeing signs that indicate either a terribly over-loaded system or a poorly implemented one. Just today I finally gave up trying to surf because it was taking one and two minutes just to switch pages here on this site - others were just as bad.
Let me post a series of 3 emails (to Cox, from Cox, back to Cox) that I sent about the issue, perhaps that will give you a quick view into things (and the 'support' we're getting). To facilitate reading the emails, I'll put them in order:
First Email
Form Message
UserID:
Comments: Network is virtually unusable again today. High latency,
time-outs and packet loss is horrid. Two tracerts (one to
www.broadbandreports.com in NYC and one to Yahoo!) are below for your
review:
To www.dslreports.com (www.broadbandreports.com)
1 1 ms 1 ms 1 ms 192.168.0.1
2 10 ms 9 ms 11 ms 10.1.16.1
3 * 163 ms * 68.12.8.129
4 * * * Request timed out.
5 140 ms 11 ms 10 ms 68.1.0.108
6 116 ms 69 ms 11 ms 68.1.0.102
7 * * 134 ms 68.1.0.107
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 230 ms 59 ms 61 ms broadbandreports.com [209.123.109.175]
Trace complete.
to Yahoo!
1 2 ms 1 ms 1 ms 192.168.0.1
2 21 ms 12 ms 79 ms 10.1.16.1
3 * 27 ms 63 ms 68.12.8.141
4 * 19 ms 15 ms 68.12.14.9
5 22 ms 13 ms 10 ms 68.1.0.104
6 * 17 ms 17 ms 68.1.0.107
7 19 ms 18 ms 35 ms gigabitethernet1-1.ipcolo1.Dallas1.Level3.net [2 09.246.152.233]
8 26 ms 28 ms 30 ms gigabitethernet10-1.core1.Dallas1.Level3.net [209.244.15.69]
9 18 ms 20 ms 21 ms so-4-0-0.mp2.Dallas1.Level3.net [209.247.10.105]
10 57 ms 59 ms 56 ms so-2-0-0.mp1.SanJose1.Level3.net [209.247.9.114]
11 60 ms 57 ms 62 ms gige9-2.ipcolo4.SanJose1.Level3.net [64.159.2.13 8]
12 65 ms 59 ms 101 ms cust-int.level3.net [64.152.69.18]
13 78 ms 75 ms 74 ms ge-1-2-0.msr2.pao.yahoo.com [216.115.100.154]
14 60 ms 62 ms 61 ms vlan28.bas1-m.snv.yahoo.com [216.115.100.122]
15 83 ms 59 ms 74 ms www.yahoo.akadns.net [216.115.102.78]
Trace complete.
submit: Submit Questions ---
Here is the reply from Cox
From: Cox eCare Oklahoma City [mailto:OklahomaCity.Services@cox.com]
Sent: Sunday, March 10, 2002 3:38 PM
To: xxxxxx
Subject: Re: Technical Support
Dear xxxxx,
Thank you for your inquiry. Cox is committed to providing the best
customer service possible.
Please visit our online tech support at the following web address. We
should be able to investigate your problem via remote control with your
permission.
»www.cox.com/OKC/RoadRunner/Onlin···port.asp
or
If you prefer the old fashioned method, you can call us at:
405-600-8282 (ed note - OKC number only).
We hope that we have been able to provide you with the information you
requested. If we have not, or if we can be of any additional service
to you, please do not hesitate to contact us again.
Thank you.
Cox Communications Online Customer Care Team
If you need additional information on other Cox products or services,
please visit our web site at »www.cox.com.
My Response to that offer to investigate via my system:
You don't seem to have a strong grasp of the obvious:
There is nothing wrong with my computer, nor my TCP/IP setup. The problem is within the CoxHSI network - Please review the attached tracert results. You may also want to visit
»Cox HSI where I am the host and you will find numerous individuals with similar, if not exactly the same problems:
»Latest status as of 3-9-02 (with analysis by site owner Justin Beech)
»Hey coxengring here is your detail
»Cox packet loss
»Strange pcket loss on 68.12.8.53 in OKC
I simply offer up evidence of a seriously problematic network and simply request that you bring the level of service and quality of service back up to the level I enjoyed for so long when it was Cox@Home vs CoxHSI.
Your comments regarding efforts to correct these problems are eagerly awaited. Naturally, Cox management and technical staff are encouraged to visit and participate in the forum (as do the Optimum Online management and staff, much to the benefit of both OOL and their customers).
Sincerely,
2kmaro of Broadband Reports
and a not as happy as I used to be CoxHSI customer
--
I am not now, nor have I ever been, a member of the Comcast Party.
==========
Late note: I've received response to last one, apparently it's all being forwarded up the line. Yaaaaaa!!!
[text was edited by author 2002-03-10 23:31:24]
[text was edited by author 2002-03-10 23:33:03] |
|
coxunhappy
join:2002-02-26
Glastonbury, CT
| reply to Shotbot
Heres what cox told me when I said everquest is no longer playable:
"keep having problems connecting to game sites, you would have to contact the game site host. We are currently not supporting any 3rd party sites such as online gaming sites."
So me getting constantly disconnected, packet loss, and lag ever since the switchover is Sony Online's fault.....
Full text:
From: Cox eCare San Diego
Reply-to: Cox eCare San Diego
Subject: Re: RE: Technical Support All headers
Dear Valued Cox Customer:
Thank you for your inquiry. Cox is committed to providing the best
customer service possible.
If you are having problems connecting to the internet altogether please
contact our technical support office for some basic troubleshooting
(1-800-234-3224). If you do have internet connection but just keep
having problems connecting to game sites, you would have to contact the
game site host. We are currently not supporting any 3rd party sites
such as online gaming sites.
I do apologize for any inconveniences you may have had.
|
|
dafish
join:1999-07-21
Glendale, AZ | LMAO.
Did you appologize for wanting to play an online game. |
|
