Micheal64
join:2002-03-05
Oklahoma City, OK | reply to Micheal64
Re: Latency in Oklahoma City
My report from off net.
»/quality/nil/697135 |
|
Micheal64
join:2002-03-05
Oklahoma City, OK
| reply to Micheal64
As I write this, I'm seeing 165ms - 250ms to the gateway (68.12.64.1) and my sons Diablo just dropped him. I checked the signal info in the modem and this is it:
Configuration
Manager
This page provides information about the current
upstream and downstream signal status of your Cable Modem.
Downstream
Value
Frequency
579000000 Hz Locked
Signal to Noise Ratio
36 dB
QAM
64
Network Access Control Object
ON
Power Level
7 dBmV
The Downstream Power Level reading is a
snapshot taken at the time this page was requested. Please
Reload/Refresh this Page for a new reading
Upstream
Value
Channel ID
1
Frequency
25008000 Hz Ranged
Ranging Service ID
873
Symbol Rate
1.280 Msym/s
Power Level
50 dBmV IMG
--
Rich Cook: Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. |
|
Micheal64
join:2002-03-05
Oklahoma City, OK
| reply to Micheal64
Papa Smurf, I don't know if you work for Cox or not, but on the off chance that you do, allow me to provide you with a bit more information.
I first reported this problem in November 2001. It wasn't nearly as often as it is now.
There have been 4 truck rolls to my residence to check line signal and such. All techs on site coordinated with the SOC here in Okc and determined that the line signal was clean and within tolerance for a HSD connection.
I live in a multi-dwelling unit with a 26 value tap. I have one internal splitter. All connections and cable have been checked and rechecked by each tech that has been on site.
The modem has been replaced once already. The account has been reprovisioned numerous times. I called again to day and the techs were seeing 25% loss when they tried to ping the ip of my gateway (68.12.64.1). The issue was supposedly handed off to Jacob (Supervisor here in Okc that I used to work for when I worked there). I don't know what else to do short of walking to the 10th street location and personally request to speak to the HSD rep at the SOC to have them actually telnet into the router and pull stats from the interface itself. I can't do much of anything else from here except grip and complain and honestly, I don't like having to do that since I know what the other end is like.
There are currently 3 Remedy tickets for this issue. The third opened yesterday. |
|
