| Slower than 90% of the US. Woo! Very good service the past few days
|
|
| Great speed!
Well worth the $50+ dollars you likely spend on it monthly! |
|
 tobyTroy Mcclure
join:2001-11-13
Seattle, WA
 ·OlyPen, Inc.
·CenturyLink
| reply to othehorror
Yep, mine is only slower than 77% of the US.
I wonder how much of the lower 20% is CL.
|
|
|
|
| reply to othehorror
This happens here almost every day. Nobody at CenturyLink cares, except for the people on that reachout team (who can't do much of anything when it's a physical lack of bandwidth that CL refuses to address).
I've started submitting FCC complaints every day things are like this. I've also been trying to get the attention of sites like The Consumerist (without luck so far). Probably going to start writing stuff on Ripoff Report soon as well. |
|
| reply to othehorror
Hello everyone, this is B with the CenturyLink Help Team. As terminx mentioned, we do care, and we'll be happy to take a look at your DSL lines for any issues. It is true that we can't fix everything, but we can help to resolve most any issues/questions you may have.
If we can help, please e-mail us at TalkToUs@CenturyLink.com, and we'll be happy to help.
Thanks,
B
CenturyLink Help Team |
|
 CheesePremium
join:2003-10-26
Naples, FL
kudos:1 | reply to othehorror
I get over 100+ms to my TF2 server, 40-50 with Comcast, CL didn't care....sad really. It's my only option here. |
|
| reply to CenturyLink
Please look into Ogden s main CO, Far end errors like crazy. Qwest modems is having hard times keeping sync. My linksys X2000 will stay sync'd but not way of looking at the line stats.
The qwest modem will connect higher but then retrains lower.
Near End CRC Errors: 1
Far End CRC Errors: 1120
30 Minute Near End CRC: 0
30 Minute Far End CRC: 29
Near End RS FEC: 68
Far End RS FEC: 88803
30 Minute Near End FEC: 0
30 Minute Far End FEC: 2538
Just after a reboot and refresh
Channel Type: Interleaved
Near End CRC Errors: 1
Far End CRC Errors: 1689
30 Minute Near End CRC: 0
30 Minute Far End CRC: 23
Near End RS FEC: 68
Far End RS FEC: 141757
30 Minute Near End FEC: 0
30 Minute Far End FEC: 2329
Something is up with Ogdens servers. |
|
| Did you fix something?
The errors stopped   |
|
| reply to othehorror
This was a major problem just a few months ago. Now it is happening again. I have high latency to the gateway and slow speeds from about 7PM to at least Midnight. I also have packet loss. Playing multiplayer games online is very frustrating.
Here's a tracert. Two timeouts on the first hop.
Tracing route to google.com [74.125.113.103]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms DD-WRT [192.168.1.1]
2 1 ms 1 ms 1 ms 192.168.2.1
3 * * 165 ms nc-184-3-24-1.dhcp.embarqhsd.net [184.3.24.1]
4 167 ms 168 ms 167 ms nc-184-3-159-49.sta.embarqhsd.net [184.3.159.49]
5 165 ms 186 ms 165 ms host.lightcore.net [206.51.88.118]
6 174 ms 175 ms 176 ms bb-asbnvacy-jx9-02-ae3.0.core.centurytel.net [208.110.248.170]
7 174 ms 174 ms 173 ms bb-asbnvacy-jx9-01-ae0.0.core.centurytel.net [208.110.248.117]
8 174 ms 173 ms 173 ms 72.14.219.254
9 175 ms 191 ms 173 ms 209.85.252.46
10 188 ms 187 ms 187 ms 209.85.241.222
11 186 ms 203 ms 186 ms 209.85.251.228
12 * * 193 ms 209.85.243.1
13 186 ms 185 ms 185 ms vw-in-f103.1e100.net [74.125.113.103]
Trace complete.
Here's a ping test to the first hop.
Pinging 184.3.24.1 with 32 bytes of data:
Reply from 184.3.24.1: bytes=32 time=164ms TTL=253
Reply from 184.3.24.1: bytes=32 time=165ms TTL=253
Reply from 184.3.24.1: bytes=32 time=165ms TTL=253
Request timed out.
Reply from 184.3.24.1: bytes=32 time=166ms TTL=253
Reply from 184.3.24.1: bytes=32 time=163ms TTL=253
Reply from 184.3.24.1: bytes=32 time=165ms TTL=253
Request timed out.
Reply from 184.3.24.1: bytes=32 time=164ms TTL=253
Reply from 184.3.24.1: bytes=32 time=165ms TTL=253
Ping statistics for 184.3.24.1:
Packets: Sent = 10, Received = 8, Lost = 2 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 163ms, Maximum = 166ms, Average = 164ms
|
|
| I do have to step up and say something.
I have 3 different ISPs.
Comcast 30/7
Qwest/Century-link 7/896k
Clearwire about 10/1
When this stuff starts to happen, I check all my other ISPs and it seems to make it's way to all of them. Comcast SNR drops to around 34db from 36db normal , Clears SNR stays fine but the speed drops to around 3Mb from around 8-10Mb and Qwest gets Far end errors like crazy, low sync and random retrains.
I would love to be able to point a finger at one ISP but when all of them show signs of the same thing.
You be the judge of whats going on, cause really being an IT specialist I can't give you an exact reason. Personally I think we are just getting more and more people on at the same time and our whole infrastructure can't handle it. The ISPs need to add double what they might be planning next. Instead of just one more RT add 2 or 3 cause in 5 years they will all me maxed out.
Anyways Peace, Nugz |
|
| reply to othehorror
Pathetic excuse for a damn ISP |
|
CheesePremium
join:2003-10-26
Naples, FL
kudos:1 | reply to Nugz
said by Nugz :I do have to step up and say something.
I have 3 different ISPs.
Comcast 30/7
Qwest/Century-link 7/896k
Clearwire about 10/1
When this stuff starts to happen, I check all my other ISPs and it seems to make it's way to all of them. Comcast SNR drops to around 34db from 36db normal , Clears SNR stays fine but the speed drops to around 3Mb from around 8-10Mb and Qwest gets Far end errors like crazy, low sync and random retrains.
I would love to be able to point a finger at one ISP but when all of them show signs of the same thing.
You be the judge of whats going on, cause really being an IT specialist I can't give you an exact reason. Personally I think we are just getting more and more people on at the same time and our whole infrastructure can't handle it. The ISPs need to add double what they might be planning next. Instead of just one more RT add 2 or 3 cause in 5 years they will all me maxed out.
Anyways Peace, Nugz
If it's ALL 3, that sounds like a problem on your end... |
|
| reply to ghjjf
said by ghjjf:
Pathetic excuse for a damn ISP
If it helps any, my iPhone gets about 20 times faster download speeds going 80 miles per hour down a highway than your CenturyLink DSL connection. Soooo pathetic. |
|
| reply to othehorror
High latency to the gateway even during nonpeak hours now. Yesterday it took me about 5 hours(maybe more) to download a 700mb file at around 30KB/sec. Speeds fluctuate between .40mbps and 1.5mbps(staying closer to .40mbps during peak hours). I guess I should mention I have the 3mbps service. The most frustrating part is packet loss. It makes online gaming impossible. Online games don't use much bandwidth either, only about 30KB/S max down and a little less on the upload. Factor in packet loss with high latency and you've got a disaster of a game. I would only recommend Centurylink for casual users who look at cat pictures.
Ping test from a few minutes ago from my Linux terminal. No packet loss yet, but during peak hours there will be.
PING 184.3.24.1 (184.3.24.1) 56(84) bytes of data.
64 bytes from 184.3.24.1: icmp_req=1 ttl=253 time=164 ms
64 bytes from 184.3.24.1: icmp_req=2 ttl=253 time=166 ms
64 bytes from 184.3.24.1: icmp_req=3 ttl=253 time=166 ms
64 bytes from 184.3.24.1: icmp_req=4 ttl=253 time=165 ms
64 bytes from 184.3.24.1: icmp_req=5 ttl=253 time=167 ms
64 bytes from 184.3.24.1: icmp_req=6 ttl=253 time=166 ms
64 bytes from 184.3.24.1: icmp_req=7 ttl=253 time=161 ms
64 bytes from 184.3.24.1: icmp_req=8 ttl=253 time=166 ms
64 bytes from 184.3.24.1: icmp_req=9 ttl=253 time=165 ms
64 bytes from 184.3.24.1: icmp_req=10 ttl=253 time=165 ms
^C
--- 184.3.24.1 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 161.698/165.507/167.310/1.496 ms
|
|
| I had the same problem and they sent a tech out. Tech said theres problem with the whole eastern NC. He installed a 10mb connection wand was getting .4. He has made several complaints to the guys upstairs and they says there is nothing wrong with the system at all.
This is the fastest its been in 3 days.
 |
|
| I haven't noticed any performance problems today. I figured it was a problem that more users besides me was experiencing. I've never had any problems on my end that they've had to come out to fix. Hopefully the performance won't degrade as we progress into the evening hours. |
|
| Im paying for 5MB it seems to fluctuate from .3 to 5mb down. Very inconsistent, ping seems normal though. Techs were supposed to be on a conference call at 9 this morning maybe they fixed it? |
|
| Just because it's working fine now doesn't mean it won't be later. I mentioned earlier that this same thing occurred several months back. For weeks my service was slow and sluggish at night time. The forums here were full of people complaining about the service in NC. Surely they won't let it get that bad. I'm crossing my fingers. |
|
ober0n
join:2003-02-09
Angier, NC | reply to Eastern NC
I wish I could have the 3Mb that I pay for. Here in Angier NC
 |
|
| Service isn't as bad as it has been but there is no excuse for such high latency to the ISP Gateway. No packet loss at least.
Pinging 184.3.24.1 with 32 bytes of data:
Reply from 184.3.24.1: bytes=32 time=148ms TTL=253
Reply from 184.3.24.1: bytes=32 time=165ms TTL=253
Reply from 184.3.24.1: bytes=32 time=166ms TTL=253
Reply from 184.3.24.1: bytes=32 time=157ms TTL=253
Reply from 184.3.24.1: bytes=32 time=166ms TTL=253
Reply from 184.3.24.1: bytes=32 time=154ms TTL=253
Reply from 184.3.24.1: bytes=32 time=158ms TTL=253
Reply from 184.3.24.1: bytes=32 time=143ms TTL=253
Reply from 184.3.24.1: bytes=32 time=148ms TTL=253
Reply from 184.3.24.1: bytes=32 time=149ms TTL=253
Ping statistics for 184.3.24.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 143ms, Maximum = 166ms, Average = 155ms
|
|
