catseyenu
Ack Pfft
Premium
join:2001-11-17
Fix East
| reply to Micheal64
Re: Latency in Oklahoma City
Sorry PapaSmurf,
Was getting a little frustrated this morning as it took 2 hours to get that post up (browser kept timing out).
»/quality/nil/700028
»/quality/nil/699018
»/quality/nil/697473
»/quality/nil/687345 |
|
Zar
Premium
join:2001-08-04
Platte City, MO
| reply to Micheal64
»/quality/nil/700045
»/quality/nil/700026
»/quality/nil/700013
--
Don't knock on deaths door, ring the bell and run, he hates that. |
|
toy4x4
join:2001-06-26
Jenks, OK | reply to Micheal64
Continuing my daily posts from this thread over here.
Original Thread:
»Hey coxengring here is your detail |
|
toy4x4
join:2001-06-26
Jenks, OK
| reply to Micheal64
That is today. Not a pretty picture.
Here is yesterday's line quality:
»/quality/nil/698944
And today's line quality test:
»/quality/nil/700082
This line test was taken after the last big spike above.
[text was edited by author 2002-03-14 16:54:45] |
|
Micheal64
join:2002-03-05
Oklahoma City, OK
| reply to PapaSmurf
said by PapaSmurf:
Dredster,
(snip)
Your concerns are not being treated lightly, and I'm working with all the right people to make sure we get the traction we need to get this resolved. Bottom line - don't worry about what you heard. The issue is not closed. Hope that helps.
As long as the issue isn't sitting idle while they wait for a couple of hundred more folks on the node to do something, I can handle it. I was always told to inform the SOC of any issues that may be even remotely related to a node issue so they could take care of it before it got out of hand. Then for this to be said to me, that just blew my mind. If you can pull off a miracle, I'll tip my hat to you oh wise blue dude. |
|
catseyenu
Ack Pfft
Premium
join:2001-11-17
Fix East | reply to Micheal64
Was at a friends house on the southside and thought I'd run a test from his box. Ouch!
He was having problems before the conversion and says they have gotten worse.
»/quality/nil/700091 |
|
toy4x4
join:2001-06-26
Jenks, OK | reply to Micheal64
Bad night...
»/quality/nil/700399 |
|
jparn1
join:2002-01-29
Oklahoma City, OK
|  reply to Micheal64
»/quality/nil/700410
Hey Dredster, this is the kind of reports I have been getting for about the last 3 months. I need to quit running these tests because they just make me mad and Cox does not seem interested in solving these problems. I think it is time to go fishing. I don't need Cox Cable for that! Still Disgusted in OKC. |
|
Zar
Premium
join:2001-08-04
Platte City, MO | reply to Micheal64
»/quality/nil/700462 |
|
2kmaro
Think
Premium,ExMod 1 BC
join:2000-07-11
ColossalCave
clubs:  
| reply to jparn1
Actually, Cox seems quite interested in bringing the service back up to what it was. Why do you think this thread even exists? You've got two choices: work with them on this and try to help yourself, or stand off in a corner and mutter about how crappy the service is. I'm not saying don't be unhappy, but don't just stand around saying they don't seem interested - things are actually getting done through this very forum. There are Cox people reviewing its contents daily, trust me. Keep the comments, complaints and the "evidence" of the problems coming - without the line quality test results, tracert results and similar stuff they are pretty much stumbling around in the dark trying to "fix this - it's broken" -- with them, they have indicators of where the problem spots are and what is wrong with them.
--
I am not now, nor have I ever been, a member of the Comcast Party. |
|
powerhog
Stinkin' up the joint
Premium
join:2000-12-14
Owasso, OK
 ·AtlasOK
| reply to Micheal64
There may be interest, but it doesn't seem there is any action. It's quite obvious there are at least two routers 68.12.14.14 and 68.12.14.10 that are having problems. They've been having problems for a long time and I think we've shown that conclusively. So why aren't they fixed?
Besides, does anyone else find it extremely sad and bothersome that we, the Cox customers, are having to troubleshoot Cox's network for them? If their NOC can't see 10% (or more) packet loss on the network, then they need some new monitoring tools or new personnel to run them! Heck, my connection is a lot better than most everyone's here but it is getting tiresome to see these problems continue. »/quality/nil/700768 |
|
PapaSmurf
A Smurfy Salute
VIP
join:2001-08-05
smurfville | reply to 2kmaro
said by 2kMaro:
things are actually getting done through this very forum
Yes they are indeed. |
|
BillRoland
Premium
join:2001-01-21
Ocala, FL
clubs:
 ·Cox HSI
| reply to powerhog
Well, if Cox has 780,000 users of its Cox HSI service, its kind of hard to track down a "problem" on 20 bitter people's connection. Now I understand that a lot of those users would have no idea if they were experiencing packet loss, but there are no mass protests for better service, outside the 10 or 20 people on this board who just want to complain and feel bitter because their being denied something they magically think they're entitled to, so no, the service doesn't suck for everyone. Obviously 68.12.14.14 and 68.12.14.10 have problems, but I tend to give Cox a little more credit than most. I'm sure the issue is a little more serious than "they just don't want to fix it," and I would bet money that they are working on it.
said by powerhog:
Besides, does anyone else find it extremely sad and bothersome that we, the Cox customers, are having to troubleshoot Cox's network for them?
If you aren't willing to help Cox out, then don't complain when your connection still sucks, and everyone else's doesn't.
--
"Do your duty in all things. You cannot do more. You should never wish to do less." Robert E. Lee |
|
Zar
Premium
join:2001-08-04
Platte City, MO
| reply to Micheal64
March 15 2002 9:40am |
|
toy4x4
join:2001-06-26
Jenks, OK
| reply to Micheal64
Here's todays.
»/quality/nil/700817
BillRoland,
Network equipment and issues are not that hard to deal wiht. Check the config of the equipment, check the cables, call the vendor. It's not magical. |
|
Micheal64
join:2002-03-05
Oklahoma City, OK
| reply to BillRoland
said by BillRoland:
Well, if Cox has 780,000 users of its Cox HSI service, its kind of hard to track down a "problem" on 20 bitter people's connection.
Oh Please!
Cox MTC - fiber ring - node - feeder cable - tap - coax drop at residence (and possible amp) - cable modem - nic cat5 - PC.
That's your rough path and your primary locations for points of failure on any Cox HSI residential link. Of course it can be different if you're running a hub/switch/router etc. Regardless of what you have at your end, at each point up to the TAP, you can remotely enter that equipment and pull statistics and do a preliminary check to see what may be happening. Most of the failures are at the tap or farther down toward the pc. My particular problem is apparently upstream at the node. That's being worked on now but it took them 6 months to actually check it. It took tier 2 less than 45 seconds to find the problem once they actually looked AT the node data. Latency at a router is much easier to see. You just try to pass traffic through it at a consistant interval to poll your stats. Then you telnet into the router and check the interface in question to see if it's having problems or if all interfaces are having problems. If it's the only one having a problem, you check the circuit. If the circuit is clean and has good quality signal, you replace the card. If it doesn't clear up, you move the circuit to an empty port on another card in case the slot is having problems. If you are authorized to do card level maintenance (most techs no longer are and you'll rma the card back to vendor) you check your test points on the card for the proper values. When you locate the one that fails, you replace the component that is causing the problem, retest the card and put the unit back into circulation.
Yea, there are times that it will take time to locate a problem. I won't argue that. I will argue the point that it's "difficult to track down". You can get a good general point of failure if one just looks at the available data instead of denying there's an actual problem.
With all that said, I would like to point out that there are individuals that are monitoring this and other groups and I applaud them for that as they're doing what they can to get these issues corrected. It's not their fault that the issues are occuring, nor is their fault that they apparently went unnoticed for so long. I appreciate the work that they're doing to raise the service level of all parties effected by these issues and I'm grateful for their assistance. As you may not know, many of us have had this tango with Cox and upper tech support for some time and are obviously growing weary of the battle. To others, this is a new problem for them. If there were more individuals like those that are trying to make a difference, I feel that many of the problems that we as customers are currently seeing would never have surfaced and would have been corrected before they were seen by the masses.
Dredster |
|
2kmaro
Think
Premium,ExMod 1 BC
join:2000-07-11
ColossalCave
clubs:
| reply to BillRoland
BillRoland - old adage "If aren't part of the solution, then you must be part of the problem".
Regardless of whether it is 2, 20, 200, 2000, 20,000 or 200,000 people - the fact of the matter is that our voice is being heard in here, and that helps all those that don't know any better.
I believe most, if not all, participants in this thread have contributed to a solution by providing examples of the problems they've encountered. And since this thread is dedicated to the OKLAHOMA CITY area, specifically, we're definitely talking of representatives of a number considerably smaller than 780,000 (at least I don't think Cox has EVERYbody in OKC signed up!:)).
And I agree 100% with your statement of "If you aren't willing to help Cox out, then don't complain when your connection still sucks, and everyone else's doesn't."
--
I am not now, nor have I ever been, a member of the Comcast Party. |
|
jparn1
join:2002-01-29
Oklahoma City, OK
| reply to 2kmaro
hey man, if cox was interested, maybe they could find the time to make good on their promise to call me back from customer service to adjust my bill. Been waiting for that call for about 3 weeks now. I cant get help with my complaint thru the normal channels because it has been excalated to management. I had my line monitored for 10 days and gave Kirk Reynolds access to my password and name so he could view the reports himself. He told me that all these tests we are doing here at DSL Reports do not really mean much. Go Figure! So do I think they have much interest in correcting these problems? No not really..... I submitted every kind of trace report and Line Quality test and gave Cox access to my equipment and about everything else they wanted until I got tired of going in circles. So dont come off with "submit tests or quit complaining" because I been there and done that and I am no better off than when I started. If u work for Cox then quit blowing smoke and give us what we r paying for. I been trying to get help since Thanksgiving on this problem. I been paying for crappy service and I am still trying to get Cox to look at the tests and address the obvious issues. Still Disgusted in OKC! |
|
Zar
Premium
join:2001-08-04
Platte City, MO
| reply to Micheal64
My fav router still lossing packets like a champ. every 20 seconds ALL DAY..
And they want to come to my house. Sorry 68.12.8.53 is not at my house!!!
--
Don't knock on deaths door, ring the bell and run, he hates that. |
|
Micheal64
join:2002-03-05
Oklahoma City, OK | 500ms and 800ms between me and my gateway.. Same old same old 
»/quality/nil/699467 |
|
