| |
to sinshiva
Re: [CenturyTel] dear centurytel/centurylinkI know I'm in a different part of the country, but, I too was having slowdowns yesterday, then the internet went off for 15 mins starting at midnight and came back up normal.. Definitely them doing some updates then a reboot. |
|
| |
to sinshiva
Hey there, sorry for the persistent connection issue. I'm happy to help with this. Send me your account information and modem/router details here; » bit.ly/IArNltThanks, ^AshleyKay |
|
|
 your moderator at work
 hidden : Friendly delete
|
| |
to sinshiva
Re: [CenturyTel] dear centurytel/centurylinkwell, it's a little after noon, locally;
admin@nerieus:/tmp/home/root# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=48 time=14.751 ms
64 bytes from 8.8.8.8: seq=1 ttl=48 time=14.428 ms
64 bytes from 8.8.8.8: seq=2 ttl=48 time=14.427 ms
64 bytes from 8.8.8.8: seq=3 ttl=48 time=14.673 ms
64 bytes from 8.8.8.8: seq=4 ttl=48 time=14.656 ms
64 bytes from 8.8.8.8: seq=5 ttl=48 time=14.399 ms
64 bytes from 8.8.8.8: seq=6 ttl=48 time=14.850 ms
64 bytes from 8.8.8.8: seq=7 ttl=48 time=14.625 ms
64 bytes from 8.8.8.8: seq=8 ttl=48 time=13.879 ms
64 bytes from 8.8.8.8: seq=9 ttl=48 time=14.357 ms
64 bytes from 8.8.8.8: seq=10 ttl=48 time=14.377 ms
64 bytes from 8.8.8.8: seq=11 ttl=48 time=14.582 ms
64 bytes from 8.8.8.8: seq=12 ttl=48 time=14.565 ms
64 bytes from 8.8.8.8: seq=13 ttl=48 time=14.807 ms
64 bytes from 8.8.8.8: seq=14 ttl=48 time=14.568 ms
64 bytes from 8.8.8.8: seq=15 ttl=48 time=13.841 ms
64 bytes from 8.8.8.8: seq=16 ttl=48 time=14.292 ms
64 bytes from 8.8.8.8: seq=17 ttl=48 time=14.284 ms
64 bytes from 8.8.8.8: seq=18 ttl=48 time=14.501 ms
64 bytes from 8.8.8.8: seq=19 ttl=48 time=14.267 ms
64 bytes from 8.8.8.8: seq=20 ttl=48 time=14.729 ms
64 bytes from 8.8.8.8: seq=21 ttl=48 time=14.497 ms
64 bytes from 8.8.8.8: seq=22 ttl=48 time=14.482 ms
64 bytes from 8.8.8.8: seq=23 ttl=48 time=14.255 ms
64 bytes from 8.8.8.8: seq=24 ttl=48 time=14.196 ms
64 bytes from 8.8.8.8: seq=25 ttl=48 time=14.486 ms
--- 8.8.8.8 ping statistics ---
26 packets transmitted, 26 packets received, 0% packet loss
round-trip min/avg/max = 13.841/14.452/14.850 ms
awesome stuff. |
|
 Tivon
join:2008-10-31
Tallahassee, FL |
Tivon
Member
2014-Jan-16 8:27 pm
I got booted from a few BF4 servers last night for high latency.  It's 8PM and Latency is not looking good.  |
|
| |
damn, missed the post otherwise i'd have tested myself. i'm pretty sure my connection was decent all day, but i wasn't doing much on it at that time |
|
nonymous (banned)
join:2003-09-08
Glendale, AZ |
to ArizonaSteve
said by ArizonaSteve:I'd like to check that myself but there's no tracert in Linux! Windows has a lot of tracert utilities but Linux doesn't, Weird! So anyway I got out my Windows laptop and checked it but the longest ping time is just 70ms since I connect to Qwest in Phoenix then go right to Los Angeles. Huh? Linux has traceroute and other commands. |
|
Tivon
join:2008-10-31
Tallahassee, FL |
to sinshiva
I've got word from Joey Harper (Social Media Manager @ CL) that tech support did find some congestion on those routers that we are seeing in the data. At this time the latency is still within spec (less than 300ms) so they weren’t able to escalate it yet. What they’re wanting to do is see if we can get more users in the area to provide their account information to escalate also.
The problem here is I only know two people with CenturyLink Internet and both have Prism and both are located on different networks entirely across town. Everyone else I know in Tallahassee FL is using Comcast Cable. I'm also not sure what they mean by "within spec" because in my games the pings jump wildly into the 300 ~ 400 range, what happens next is I'm ejected by the admins for high latency, then I check the internet, take the pingplotter pictures and send them in. Not sure what else I can do from my end?
I should just let the engineers do what they can for now. You never know what could be going on out there in the world, maybe millions of torrent users or DDOS bots, who knows? But seriously if this keeps going on, granted I hate sounding like a threat, the practicality of the situation will steer my needs into the arms of another service provider, one with a connection that is not congested. Perhaps leasing a Cable Internet connection for a few months would give me some idea of what works best in this area.
|
|
| Tivon |
Tivon
Member
2014-Jan-17 1:13 pm
Taking ping pictures at 1PM, so far calm waters and smooth sailing. Speedtest.net is showing good numbers. I see a Lag-shark at 208.110.248.133, 208.110.248.74 and 208.110.248.57 on pingplotter, so far not hungry enough to eat people. |
|
| |
to sinshiva
i sent him an e-mail with my information just a little while ago; what happens when you ping your first hop outside of your network? it's been looking good for me, but i'll monitor this thread to see if i am getting similar results to the routers that are causing you trouble
ping 67.233.128.1
Pinging 67.233.128.1 with 32 bytes of data:
Reply from 67.233.128.1: bytes=32 time=7ms TTL=254
Reply from 67.233.128.1: bytes=32 time=6ms TTL=254
Reply from 67.233.128.1: bytes=32 time=7ms TTL=254
Reply from 67.233.128.1: bytes=32 time=6ms TTL=254
Ping statistics for 67.233.128.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 7ms, Average = 6ms
edit: i see you are still getting that 22ms to your first hop. that does seem abnormally high to me, even if this might be considered downtime for traffic in our city. |
|
sinshiva
1 edit |
to Tivon
208_110_248_74 |
i tried every router in your path, but only found one that gave me interesting results; ASUSWRT-Merlin RT-N66U_3.0.0.4 Fri Jan 17 05:14:13 UTC 2014 admin@nerieus:/tmp/home/root# ping 208.110.248.74 PING 208.110.248.74 (208.110.248.74): 56 data bytes 64 bytes from 208.110.248.74: seq=0 ttl=61 time=8.146 ms 64 bytes from 208.110.248.74: seq=1 ttl=61 time=10.687 ms 64 bytes from 208.110.248.74: seq=2 ttl=61 time=7.705 ms 64 bytes from 208.110.248.74: seq=3 ttl=61 time=7.692 ms 64 bytes from 208.110.248.74: seq=4 ttl=61 time=7.685 ms 64 bytes from 208.110.248.74: seq=5 ttl=61 time=7.689 ms 64 bytes from 208.110.248.74: seq=6 ttl=61 time=10.625 ms 64 bytes from 208.110.248.74: seq=7 ttl=61 time=27.412 ms 64 bytes from 208.110.248.74: seq=8 ttl=61 time=7.939 ms 64 bytes from 208.110.248.74: seq=9 ttl=61 time=7.916 ms 64 bytes from 208.110.248.74: seq=10 ttl=61 time=7.426 ms 64 bytes from 208.110.248.74: seq=11 ttl=61 time=7.613 ms 64 bytes from 208.110.248.74: seq=12 ttl=61 time=19.230 ms 64 bytes from 208.110.248.74: seq=13 ttl=61 time=64.065 ms 64 bytes from 208.110.248.74: seq=14 ttl=61 time=7.616 ms 64 bytes from 208.110.248.74: seq=15 ttl=61 time=7.826 ms 64 bytes from 208.110.248.74: seq=16 ttl=61 time=7.842 ms 64 bytes from 208.110.248.74: seq=17 ttl=61 time=7.583 ms --- 208.110.248.74 ping statistics --- 18 packets transmitted, 18 packets received, 0% packet loss round-trip min/avg/max = 7.426/12.927/64.065 ms every other router in the path gave me consistent 6/7ms until i hit georgia, where it turns into 13/14ms this could be a sign somebody was actively working on that specific router, but i'd keep an eye on it attached a picture of pinging that router and 8.8.8.8 simultaneously |
|
Tivon
join:2008-10-31
Tallahassee, FL
1 edit |
Tivon
Member
2014-Jan-17 1:39 pm
Checking on the 208.110.248's, hard to say if anything is wrong just yet without the super high latency problem taking place. I can still remember when anything below 150ms ping was good on copper lines. You can sure tell they moved to fiber, just wish I was seeing those low pings that you are getting sinshiva. Edit. Changing PingPlotter Freeware options to show more Samples. After this I'm going to wait until 8 ~ 11pm when traffic is higher. |
|
1 edit |
i will check up on the thread periodically and post results around 8-9pm.
edit: as of 6pm, still see 6-8ms to your first hop; only fluxuating a bit because we have netflix streaming atm |
|
| sinshiva |
to sinshiva
crazy results atm.
i started out testing tivon's first couple hops
1st: clean
ping 67.233.128.1
Pinging 67.233.128.1 with 32 bytes of data:
Reply from 67.233.128.1: bytes=32 time=7ms TTL=254
Reply from 67.233.128.1: bytes=32 time=7ms TTL=254
Reply from 67.233.128.1: bytes=32 time=7ms TTL=254
Reply from 67.233.128.1: bytes=32 time=7ms TTL=254
Ping statistics for 67.233.128.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 7ms, Average = 7ms
2nd: clean
ping 67.235.242.97
Pinging 67.235.242.97 with 32 bytes of data:
Reply from 67.235.242.97: bytes=32 time=7ms TTL=62
Reply from 67.235.242.97: bytes=32 time=8ms TTL=62
Reply from 67.235.242.97: bytes=32 time=7ms TTL=62
Reply from 67.235.242.97: bytes=32 time=7ms TTL=62
Ping statistics for 67.235.242.97:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 8ms, Average = 7ms
3rd: clean
ping 67.232.255.193
Pinging 67.232.255.193 with 32 bytes of data:
Reply from 67.232.255.193: bytes=32 time=7ms TTL=61
Reply from 67.232.255.193: bytes=32 time=7ms TTL=61
Reply from 67.232.255.193: bytes=32 time=7ms TTL=61
Reply from 67.232.255.193: bytes=32 time=7ms TTL=61
Ping statistics for 67.232.255.193:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 7ms, Average = 7ms
4th: wow, this is ugly
ping 208.110.248.133
Pinging 208.110.248.133 with 32 bytes of data:
Reply from 208.110.248.133: bytes=32 time=100ms TTL=59
Reply from 208.110.248.133: bytes=32 time=218ms TTL=59
Reply from 208.110.248.133: bytes=32 time=81ms TTL=59
Reply from 208.110.248.133: bytes=32 time=160ms TTL=59
Ping statistics for 208.110.248.133:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 81ms, Maximum = 218ms, Average = 139ms
it's all ugly after that. so i tested my own connection to 8.8.8.8
ping 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=170ms TTL=47
Reply from 8.8.8.8: bytes=32 time=166ms TTL=47
Reply from 8.8.8.8: bytes=32 time=192ms TTL=47
Reply from 8.8.8.8: bytes=32 time=302ms TTL=47
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 166ms, Maximum = 302ms, Average = 207ms
ALL games are completely unplayable right now. this is most unusual. i'll wait an hour to see if it goes back to normal, but i shouldn't have to... |
|
Tivon
join:2008-10-31
Tallahassee, FL
1 edit |
Tivon
Member
2014-Jan-17 9:59 pm
I did some traces while trying to watch some Twitch.tv streams tonight and the videos just spin endlessly buffering. (It's been doing this off and on for the last year!!!) So much for paying the extra money for 10 down service. I guess my money is not good enough for CenturyLink? lol I had 56K dial-up pings faster than this 10+ years ago.  |
|
Tivon
2 edits |
Tivon
Member
2014-Jan-17 10:20 pm
Tossing in another Ping Plotter of 208.110.248.133 that you said looks bad. It does act wonky but I'm also seeing unusual pings from 67.235.254.233 Edit* I can't play BF4 right now or I'll be kicked from the game for high latency. The only reason I have internet is for surfing, games and e-mail. Surfing working kind of if you subtract the Twitch.TV streaming problem, Games work if I subtract the loss of time spent playing when ejected for latency and E-mail is probably work related spam. Starting to lose my temper, blood pressure is high. |
|
| |
ping 67.235.254.233
Pinging 67.235.254.233 with 32 bytes of data:
Reply from 67.235.254.233: bytes=32 time=13ms TTL=252
Reply from 67.235.254.233: bytes=32 time=14ms TTL=252
Reply from 67.235.254.233: bytes=32 time=14ms TTL=252
Reply from 67.235.254.233: bytes=32 time=14ms TTL=252
Ping statistics for 67.235.254.233:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 14ms, Average = 13ms
got netflix streaming atm, too. i think the hop after is possibly affecting your 67.235.254.233 hop. my tracert is clear up until it hits the 208. ips |
|
Tivon
join:2008-10-31
Tallahassee, FL
1 edit |
Tivon
Member
2014-Jan-17 11:17 pm
I thought this might be interesting. I've added a pingplotter from my brothers house across town. He sent me this test once last month when he was having latency issues to one of his online games. I'll try to get him to update another test run. I never did hear from him if his calls to CL panned out. As you can see there is some max latency on some familiar number ranges. Edit* Installed another version of the PingPlotter program, it's also Free. PingPlotter Standard Edition 3.40.2s. Testing 8.8.8.8 again. The numbers seem to be dropping down into the 100 ~ 150ms range. Maybe I'll get some game time in before hitting the bed for work in the morning. |
|
| |
i am going to wait til the same problematic hours to test and see if anything was fixed. if not and i get response like 'sorry, but everybody is using the internet so you dont get to', i'm going to be livid |
|
Tivon
join:2008-10-31
Tallahassee, FL
4 edits |
Tivon
Member
2014-Jan-18 8:28 pm
Oh I'm very Livid! I got 3 hours of sleep, worked 12 long hours, payed my bills, come home to this [BLEEP] of a [CENSOR!] network and I can't play any games or watch any Twitch.tv streams smoothly. Never mind everyone you can all go home now this is "within spec." Perhaps my next payment as a life long customer will suddenly fall "within spec" of "never" because they are not taking this matter seriously or else it would have been fixed by now. Waiting on that new modem so I can toss this time waster out the window and go in for the kill. Maybe this what they want though, oversold their network and would rather people that are smart enough to know better get upset and go away?  I'm going to bed, I've had enough for one day. No point if I have to wait until after 11pm for a somewhat better connection. |
|
| |
yep, connection is ugly. |
|
| sinshiva |
to Tivon
googledns | 
level3dns | 
yahoodotcom |
did some traces using your pingplotter software zero traffic on my lan. |
|
| sinshiva |
to Tivon
These are directly from my router. ZERO traffic on my lan.
ping to _my_ last 67. same for both tivon and i. embarq/centurylink hop
admin@nerieus:/tmp/home/root# ping 67.232.254.233
PING 67.232.254.233 (67.232.254.233): 56 data bytes
64 bytes from 67.232.254.233: seq=0 ttl=62 time=162.067 ms
64 bytes from 67.232.254.233: seq=1 ttl=62 time=144.063 ms
64 bytes from 67.232.254.233: seq=2 ttl=62 time=155.877 ms
64 bytes from 67.232.254.233: seq=3 ttl=62 time=151.099 ms
64 bytes from 67.232.254.233: seq=4 ttl=62 time=175.456 ms
64 bytes from 67.232.254.233: seq=5 ttl=62 time=170.890 ms
64 bytes from 67.232.254.233: seq=6 ttl=62 time=188.734 ms
64 bytes from 67.232.254.233: seq=7 ttl=62 time=154.359 ms
64 bytes from 67.232.254.233: seq=8 ttl=62 time=152.532 ms
64 bytes from 67.232.254.233: seq=9 ttl=62 time=162.842 ms
64 bytes from 67.232.254.233: seq=10 ttl=62 time=174.794 ms
64 bytes from 67.232.254.233: seq=11 ttl=62 time=172.139 ms
64 bytes from 67.232.254.233: seq=12 ttl=62 time=185.030 ms
64 bytes from 67.232.254.233: seq=13 ttl=62 time=168.743 ms
64 bytes from 67.232.254.233: seq=14 ttl=62 time=148.529 ms
64 bytes from 67.232.254.233: seq=15 ttl=62 time=173.418 ms
64 bytes from 67.232.254.233: seq=16 ttl=62 time=174.997 ms
64 bytes from 67.232.254.233: seq=17 ttl=62 time=176.602 ms
64 bytes from 67.232.254.233: seq=18 ttl=62 time=191.620 ms
64 bytes from 67.232.254.233: seq=19 ttl=62 time=181.761 ms
64 bytes from 67.232.254.233: seq=20 ttl=62 time=167.433 ms
64 bytes from 67.232.254.233: seq=21 ttl=62 time=187.761 ms
64 bytes from 67.232.254.233: seq=22 ttl=62 time=173.079 ms
64 bytes from 67.232.254.233: seq=23 ttl=62 time=167.399 ms
64 bytes from 67.232.254.233: seq=24 ttl=62 time=176.429 ms
64 bytes from 67.232.254.233: seq=25 ttl=62 time=184.226 ms
64 bytes from 67.232.254.233: seq=26 ttl=62 time=189.026 ms
64 bytes from 67.232.254.233: seq=27 ttl=62 time=179.498 ms
64 bytes from 67.232.254.233: seq=28 ttl=62 time=168.680 ms
64 bytes from 67.232.254.233: seq=29 ttl=62 time=166.924 ms
--- 67.232.254.233 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max = 144.063/170.866/191.620 ms
ping to _my_ first centurylink 208 hop. also same for both tivon and i.
admin@nerieus:/tmp/home/root# ping 208.110.248.137
PING 208.110.248.137 (208.110.248.137): 56 data bytes
64 bytes from 208.110.248.137: seq=0 ttl=61 time=170.310 ms
64 bytes from 208.110.248.137: seq=1 ttl=61 time=156.847 ms
64 bytes from 208.110.248.137: seq=2 ttl=61 time=156.346 ms
64 bytes from 208.110.248.137: seq=3 ttl=61 time=134.677 ms
64 bytes from 208.110.248.137: seq=4 ttl=61 time=72.960 ms
64 bytes from 208.110.248.137: seq=5 ttl=61 time=127.689 ms
64 bytes from 208.110.248.137: seq=6 ttl=61 time=130.332 ms
64 bytes from 208.110.248.137: seq=7 ttl=61 time=114.422 ms
64 bytes from 208.110.248.137: seq=8 ttl=61 time=140.144 ms
64 bytes from 208.110.248.137: seq=9 ttl=61 time=107.260 ms
64 bytes from 208.110.248.137: seq=10 ttl=61 time=226.513 ms
64 bytes from 208.110.248.137: seq=11 ttl=61 time=77.916 ms
64 bytes from 208.110.248.137: seq=12 ttl=61 time=160.941 ms
64 bytes from 208.110.248.137: seq=13 ttl=61 time=76.417 ms
64 bytes from 208.110.248.137: seq=14 ttl=61 time=167.569 ms
64 bytes from 208.110.248.137: seq=15 ttl=61 time=78.741 ms
64 bytes from 208.110.248.137: seq=16 ttl=61 time=162.005 ms
64 bytes from 208.110.248.137: seq=17 ttl=61 time=140.814 ms
64 bytes from 208.110.248.137: seq=18 ttl=61 time=83.763 ms
64 bytes from 208.110.248.137: seq=19 ttl=61 time=75.100 ms
64 bytes from 208.110.248.137: seq=20 ttl=61 time=143.253 ms
64 bytes from 208.110.248.137: seq=21 ttl=61 time=144.067 ms
64 bytes from 208.110.248.137: seq=22 ttl=61 time=168.410 ms
64 bytes from 208.110.248.137: seq=23 ttl=61 time=83.970 ms
64 bytes from 208.110.248.137: seq=24 ttl=61 time=84.665 ms
64 bytes from 208.110.248.137: seq=25 ttl=61 time=169.895 ms
64 bytes from 208.110.248.137: seq=26 ttl=61 time=88.725 ms
64 bytes from 208.110.248.137: seq=27 ttl=61 time=183.828 ms
64 bytes from 208.110.248.137: seq=28 ttl=61 time=71.384 ms
64 bytes from 208.110.248.137: seq=29 ttl=61 time=88.268 ms
--- 208.110.248.137 ping statistics ---
31 packets transmitted, 30 packets received, 3% packet loss
round-trip min/avg/max = 71.384/126.241/226.513 ms |
|
 tubbynetreminds me of the danse russe
MVM
join:2008-01-16
Gilbert, AZ |
to ArizonaSteve
said by ArizonaSteve:I'd like to check that myself but there's no tracert in Linux! Windows has a lot of tracert utilities but Linux doesn't, Weird! So anyway I got out my Windows laptop and checked it but the longest ping time is just 70ms since I connect to Qwest in Phoenix then go right to Los Angeles. yes. it does. traceroute is the command you're looking for. q. |
|
Tivon
join:2008-10-31
Tallahassee, FL |
to sinshiva
Another terrible latency night in Tallahassee with CenturyLink. Posting the ping plotter images and I'm about to install the new modem. BRB.. soon. |
|
| Tivon |
to sinshiva
Okay, I've installed the new modem, wires and filters. I guess because of the new modems mac address the DHCP changed. However there is still some latency on the network... |
|
| Tivon |
to sinshiva
SpeedTest.Net & CenturyLink Speed Tests taken at random times during the same session. SpeedTest.Net is all over the place when the network Latency is poor. Give it a few hours and I'm sure those tests will return to normal speeds. The CenturyLink speed tests show good speeds but with some latency. Not sure I can trust the CenturyLink tests at the time because YouTube and Twitch.TV are buffering kind of choppy and slow. |
|
Crusty
join:2008-11-11
Sanger, TX |
Crusty
Member
2014-Jan-20 10:58 pm
said by Tivon:Not sure I can trust the CenturyLink tests at the time because YouTube and Twitch.TV are buffering kind of choppy and slow. I'd never trust the providers "on network" speed tests. On net - off net are two totally different things. |
|
| |
to Tivon
Tivon, I am located in Ohio and I have the same exact issues. Their tech support tells me there is nothing they can do because they cannot control the speed of the rest of the internet. I get 9mbps to them but to yahoo, microsoft, google, I get around 1.5mbps currently. Been this way for months. |
|
 tobyTroy Mcclure
join:2001-11-13
Seattle, WA |
to Crusty
A few good speed test sites are: » speedof.me/ and » speedtest.comcast.net/ |
|
