bigdaddyjosh
join:2005-09-22
Bossier City, LA | what the hell is this? 
Im now starting to keep records of all speed tests done. Ive filed a report with BBB as well. | |
|
 Lucent Verda
join:2007-04-05
Lake Charles, LA
| Re: what the hell is this? said by bigdaddyjosh  :Im now starting to keep records of all speed tests done. Ive filed a report with BBB as well. You should be hearing from them soon. I heard from the local office within 48 hours. They really tried to fix what they could (all involved were former Cox personnel)the ongoing problems are still there. It's mainly a bandwidth issue down here, but ping times are also a big factor. I haven't seen less than half a second since last year (avg ping time 65ms) | |
|
 | 
gatorkram
Spelling and Grammer impared
Premium
join:2002-07-22
Winterville, NC
clubs: | Re: what the hell is this? Wouldn't 500ms be 1/2 a second? Also, when talking about ping times, that is round trip.
--
Give me bandwidth or give me death! | |
|
| | Kenrin
join:2004-05-13
Greenville, NC | Re: what the hell is this? 65 is way way faster than half a second ;P | |
|
| | | 
eye4thesky
join:2005-07-10
Lumberport, WV | Re: what the hell is this? 65 for a particular hop or for the whole run? my are usually way over 65 for the complete run. | |
|
| | | | |
| | | | |
eye4thesky
join:2005-07-10
Lumberport, WV | Re: what the hell is this? maybe i need to make more clear my question. are you talking about a particular hop ping to 65 in the route or does the 65 represent the ping to your destination? | |
|
bigdaddyjosh
join:2005-09-22
Bossier City, LA
| ok well i heard back from the BBB today. This is the message.
Complaint ID#: 14xxxxxx
Business Name: Suddenlink Communications
Thank you for contacting the Better Business Bureau. Your complaint was received by the Bureau on April 19, 2007 and has been assigned case# 14003178in our files. Please make a note of this number for future reference.
Your complaint has been applied to the following business:
Suddenlink Communications
725 Benton Rd
Bossier City, LA 71111-3704
The case has been reviewed and has now been forwarded to the business for their response. This business has until May 4, 2007 to respond to your complaint. You may contact our office after May 4, 2007 to check the status of your complaint.
We encourage you to use our ONLINE COMPLAINT system to keep up with the progress of this complaint. To view the details of your case click here.
Sincerely,
Monica Free | |
|
| Lucent Verda
join:2007-04-05
Lake Charles, LA
| Re: what the hell is this? said by bigdaddyjosh :ok well i heard back from the BBB today. This is the message. Complaint ID#: 14xxxxxx Business Name: Suddenlink Communications Thank you for contacting the Better Business Bureau. Your complaint was received by the Bureau on April 19, 2007 and has been assigned case# 14003178in our files. Please make a note of this number for future reference. Trust me. they'll call. I admit my local service personnel and Management focused on fixing the problem. It took them nearly a month to get it done but they did get me a fast connection-sometimes.
Note: all involved were former Cox employees, and the biggest problem in my case is the local office was never notified that I'd called in over 14 complaints. It seems the Tyler call center is not informing the local office when there's a problem. | |
|
| | 
bd152
@suddenlink.net | Re: what the hell is this? Good luck with the BBB - they're not a government org and have no legal means to make Suddenlink do anything. If the area is oversold, Suddenlink won't do anything anyway. | |
|
bigdaddyjosh
join:2005-09-22
Bossier City, LA
| Oh and to the guys talking about tracert up top heres mine:
Tracing route to suddenlink.net [208.180.43.6]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 101 ms 81 ms 32 ms r74-193-183-1.bssrcmta01.bscyla.by.dh.suddenlink
.net [74.193.183.1]
3 267 ms 31 ms 29 ms s208-180-49-49.tylrtx.tl.sta.suddenlink.net [208
.180.49.49]
4 78 ms 199 ms 62 ms s208-180-49-37.tylrtx.tl.sta.suddenlink.net [208
.180.49.37]
5 62 ms 189 ms 100 ms s208-180-49-1.tylrtx.tl.sta.suddenlink.net [208.
180.49.1]
6 51 ms 130 ms 98 ms cdm-66-76-31-37.lfkn.cox-internet.com [66.76.31.
37]
7 186 ms 91 ms 64 ms cdm-66-76-30-149.tylrtx.suddenlink.net [66.76.30
.149]
8 144 ms 59 ms 53 ms cdm-66-76-30-129.tylrtx.suddenlink.net [66.76.30
.129]
9 136 ms 50 ms 97 ms cdm-66-76-30-2.tylrtx.suddenlink.net [66.76.30.2
]
10 127 ms 73 ms 76 ms cdm-66-76-30-70.tylrtx.suddenlink.net [66.76.30.
70]
11 62 ms 63 ms 62 ms cdm-66-76-29-28.mnwl.cox-internet.com [66.76.29.
28]
12 * * * Request timed out.
13 122 ms 275 ms 84 ms n208-180-43-6.tylrtx.tl.suddenlink.net [208.180.
43.6]
Trace complete. | |
|
| 
porkchops
...meh
Premium
join:2003-05-17
Saint Marys, WV
| Re: what the hell is this? said by bigdaddyjosh :
2 101 ms 81 ms 32 ms r74-193-183-1.bssrcmta01.bscyla.by.dh.suddenlink
.net [74.193.183.1]
It looks like an issue between the modem and the CMTS.
100ms on your first hop is just horrible, horrible, horrible. - (yes, it's that bad)
Check your internal diagnostics page on the modem, if you can.
Tech support might also be able to check the signal levels remotely. | |
|
bigdaddyjosh
join:2005-09-22
Bossier City, LA
| Downstream Value
Frequency 117000000 Hz
Signal To Noise Ratio 36.8 dB
Power Level -1.4 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 3
Frequency 33000000 Hz
Power 46.8 dBmV | |
|
| plummer2461
join:2006-04-24
Columbus, OH
| Re: what the hell is this? Tracing route to n208-180-43-6.tylrtx.tl.suddenlink.net [208.180.43.6]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 7 ms 8 ms cdm-66-76-225-177.tyrd.cox-internet.com [66.76.2
25.177]
4 11 ms 11 ms 10 ms cdm-66-76-225-165.tyrd.cox-internet.com [66.76.2
25.165]
5 83 ms 83 ms 83 ms cdm-66-76-168-13.bssr.cox-internet.com [66.76.16
8.13]
6 86 ms 86 ms 86 ms cdm-66-76-30-161.tylrtx.suddenlink.net [66.76.30
.161]
7 88 ms 87 ms 88 ms cdm-66-76-30-141.tylrtx.suddenlink.net [66.76.30
.141]
8 83 ms 96 ms 84 ms cdm-66-76-30-70.tylrtx.suddenlink.net [66.76.30.
70]
9 85 ms 94 ms 84 ms cdm-66-76-29-28.mnwl.cox-internet.com [66.76.29.
28]
10 * * * Request timed out.
11 84 ms 85 ms 89 ms n208-180-43-6.tylrtx.tl.suddenlink.net [208.180.
43.6]
Trace complete.
Boy suddenlink, that's pretty awesome, eh? I'm in parkersburg, wv. | |
|
| |
porkchops
...meh
Premium
join:2003-05-17
Saint Marys, WV
| Re: what the hell is this? said by plummber2461 :
5 83 ms 83 ms 83 ms cdm-66-76-168-13.bssr.cox-internet.com [66.76.168.13]
Isn't that router evil?
I haven't seen it resolve in less than 50ms since a few weeks after the ip changes. It used to be less than 30ms.
Either way, it's not helping their level3 problem.
-
local-routing - [8ms]
bssr.cox-internet.com - [Lose 1 Turn]
level3 addressing block - [Go Back 3 Spaces]
destination address - [Not enough packets. Do not pass go. Do not collect $200] | |
|
| | | plummer2461
join:2006-04-24
Columbus, OH | Re: what the hell is this? I don't know why my second hop request timed out. Now' I'm afraid my router might not be up to par... | |
|
| | | |
porkchops
...meh
Premium
join:2003-05-17
Saint Marys, WV
2 edits | Re: what the hell is this? Nah. Your router is fine.
Your second hop is a private network between the modem and the CMTS. It works, it's just not responding to ICMP.
192.168.1.1 is your router (hop 1).
My second hop has strange results...
Two weeks ago, it was responding "Request Timed Out"
One week ago, it was responding 10.x.x.x (like it should)
This week it responds as my router. Go figure.
-edit-
Well, that's what I get for tabbed browsing.
I'm an idiot. I'll just shut up now... | |
|
| | | | |
gatorkram
Spelling and Grammer impared
Premium
join:2002-07-22
Winterville, NC
clubs: | Re: what the hell is this? My second hop is all of a sudden not responding as well. Very odd. Something is afoot.
--
Give me bandwidth or give me death! | |
|
| | | | | | bhurmam4
join:2006-10-10
Christiansburg, VA
| Re: what the hell is this? my speeds just dropped through the floor.
Tracing route to google.com [64.233.187.99]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms DD-WRT [192.168.1.1]
2 18 ms 23 ms 27 ms 10.95.0.1
3 11 ms 11 ms 22 ms 24.197.3.42
4 53 ms 47 ms 61 ms 12.126.167.129
5 95 ms 72 ms 69 ms gbr2-p70.wswdc.ip.att.net [12.123.9.46]
6 64 ms 56 ms 61 ms tbr2-p013701.wswdc.ip.att.net [12.122.11.189]
7 67 ms 101 ms 122 ms 12.122.84.201
8 250 ms 242 ms 197 ms 192.205.34.42
9 189 ms 203 ms 204 ms ix-12-2.core3.AEQ-Ashburn.teleglobe.net [63.243.
149.102]
10 141 ms 148 ms 157 ms 209.85.130.16
11 87 ms 96 ms 87 ms 72.14.238.136
12 84 ms 156 ms 119 ms 72.14.236.15
13 109 ms 91 ms 67 ms 216.239.49.222
14 191 ms 173 ms 142 ms jc-in-f99.google.com [64.233.187.99]
Trace complete.
| |
|
bigdaddyjosh
join:2005-09-22
Bossier City, LA | iget great speeds in the morning but around 5 on weekdays my speeds drop dramatically
 | |
|
|
| areacode304
join:2006-08-26
WV
| Re: what the hell is this? I like the way you think. | |
|
bigdaddyjosh
join:2005-09-22
Bossier City, LA | I realize this but what else can I do? Dsl isn't available in my neighborhood and im not paying for satellite or my own t3 connection when fiber is 1/5 the cost just over the state line | |
|
| |
bigdaddyjosh
join:2005-09-22
Bossier City, LA
| Daarken Im smack dab in the middle of the city...This is an AIR FORCE town we have around 200000+ people. Broadband penetratation is low here. Hell, most of my friends haven't even heard of FTTH here. This is an overloaded node cut and dry my friend lives outsside of town hes has no issues whatsoever with suddenlink do to the fact that no one else lives relatively close by | |
|
bigdaddyjosh
join:2005-09-22
Bossier City, LA
| this is the response from suddenlink i just received today
BBB Processing
04/18/2007 web BBB Case Received by BBB
04/19/2007 MF BBB Case Reviewed by BBB - Member
04/19/2007 Otto EMAIL Send Acknowledgement to Consumer
04/19/2007 MF MAIL Notify Business of Dispute - Member
05/02/2007 WEB BBB RECEIVE BUSINESS RESPONSE : We are upgrding the nodes in this area over the next 30-45 days. As this upgrade is completed it should aide in correcting this issue.
nodes to be upgraded...we shall see | |
|
|
|
|
·
·
·