Topic 'Packet loss to the west coast, ping spikes to the east' in forum 'CenturyLink' - dslreports.com

Re: Packet loss to the west coast, ping spikes to the east

Fri, 20 Nov 2009 23:36:29 EDT

darcon posted : Left 4 Dead 2 came out.

Online experience is horrible thanks to constant packet loss.

Pings are all over the place when I play.

Depression setting in.

Just one more semester of school and then I can figure out where to move where the only services available aren't complete shit.

Re: Packet loss to the west coast, ping spikes to the east

Sun, 08 Nov 2009 08:44:05 EDT

anon posted : I agree Tarheels Fan the port is hosed if I'm picked and it shows sync. The point I was making is that the stats that techs are seeing while remotely viewing the DSLAM can be wrong and that I'd seen it too many times to count.

darcon is at his wits end and he believes that calling tech support would be pointless as they'll repeat what embarq_joey said. I will state that embarq_joey is one of the best things to come to this board but he is still looking remotely at the DSLAM. darcon needs to get a tech on site to either confirm or see if it's different and get a repair.

Too bad we don't have the OTT anymore and you could see how many times this happens.

Re: Packet loss to the west coast, ping spikes to the east

Sat, 07 Nov 2009 21:52:28 EDT

Go Tarheels posted : Then you obviously have a tech not doing his job. I have been doing this job for many years as well, and if your port shows sync and you have the field pair pulled, then either you have pulled the wrong pair or that port is hosed. DSLAM stats are just the other side of the CPE. Furthermore, his latency issue has absolutely nothing to do with the physical line stats. He would see loss of sync/error issues.

Re: Packet loss to the west coast, ping spikes to the east

Sat, 07 Nov 2009 18:05:14 EDT

anon posted : As great as Embarq_Joey is, and he is a big help. he's sitting in Florida or where ever and looking at a screen that is connected to your DSLAM. He's looking at the stats the card is reporting.

If any other field tech is reading this they'll back me up on this. I can't tell you how many times in the last 10 years I'm on the phone with tech support and I'm at the DSLAM with the field side picked and being told I'm in sync. I could go on and on but I'm sorry, I trust my eyes, experience and the HST-3000 DSL test box to give me the true story.

So get on the phone or the service chat and get a tech out there to test. No more whining and bitching, just do it!

Re: Packet loss to the west coast, ping spikes to the east

Sat, 07 Nov 2009 17:06:57 EDT

darcon posted :

said by Hazy Arc:

Have you called support? Have you tried sending Joey your information? Embarq isn't going to magically fix your connection from a forum post on a website.

This is the response I got from Embarq_Joey:

"Your line looks clean, definitely some issues with network routing. Problem is that our routing as you can see is through sprintlink and some customers its via Level 3. Since it's outsources as long as they are meeting their service level agreements we can't even escalate to them. Since most of your pings are below 200ms, its not something we can report to them. Hopefully whatever caused the problem is fixed soon, but for now theres not much I can do to help."

I guarantee that Joey is probably as good of support as I can get out of an American ISP. Calling support would be pointless as it would just be a repeat of this statement, although less technical I'm sure.
From what I can tell, it seems I would need 100% packet loss (lol) to qualify for anyone to give a shit.

Re: Packet loss to the west coast, ping spikes to the east

Sat, 07 Nov 2009 17:06:51 EDT

Hazy Arc posted : Have you called support? Have you tried sending Joey your information?

Re: Packet loss to the west coast, ping spikes to the east

Sat, 07 Nov 2009 16:05:31 EDT

bctrainers posted : If you have access to a linux box on your network (even a vm would do with fedora or ubuntu). Install mytraceroute aka mtr on it, than do a mtr google.com or some common address that you visit. That tool can really help you in finding out where the issues are coming from.

                                               Packets               Pings Host                                        Loss%   Snt   Last   Avg  Best  Wrst StDev 1. router.home.lan                           0.0%   322    0.7   0.7   0.2   2.8   0.2 2. ks-76-7-1-1.sta.embarqhsd.net             0.0%   322    7.2   7.4   6.2  18.5   0.9 3. ks-76-7-255-209.sta.embarqhsd.net         0.0%   322   22.1   7.6   6.4  40.6   2.6 4. ge-6-6.car2.StLouis1.Level3.net           1.2%   322   14.2  26.2  13.1 210.1  37.0 5. ae-4-4.ebr2.Chicago1.Level3.net           1.6%   322   27.2  24.1  18.7  33.6   4.4 6. ae-5.ebr2.Chicago2.Level3.net             0.3%   322   19.8  19.7  17.9  30.0   1.1 7. ae-2-2.ebr2.Washington1.Level3.net        0.3%   322   37.2  37.0  35.7  45.9   0.9 8. ae-92-92.csw4.Washington1.Level3.net      0.0%   322   47.1  42.4  36.3  54.5   4.5 9. ae-4-99.edge1.Washington1.Level3.net      0.0%   322   58.2  39.9  36.4 103.3   8.510. GOOGLE-INC.edge1.Washington1.Level3.net   0.0%   322   37.7  41.6  36.7 141.7  12.111. 209.85.241.50                             0.0%   322   39.3  40.7  38.1 132.8   7.412. 216.239.48.69                             0.0%   322   46.2  52.8  44.5 185.4  23.613. 72.14.232.213                             0.0%   322   47.1  52.2  44.7 201.9  19.1    72.14.232.21514. 209.85.253.133                            0.0%   322   56.5  51.8  44.9  77.3   4.9    209.85.253.137    209.85.253.145    209.85.253.14115. yx-in-f100.1e100.net                      0.0%   321   46.8  47.2  45.1  52.0   1.1

On windows, I'm not too sure about how this tool works but it's called pathping. pathping google.com or so. Once it does the traceroute, it will halt for a good five to ten minutes to do this test over and over again without you having to do anything. It'll appear as if your command screen is "not responding", but it is as it's running the test.

C:\Users\bc>pathping google.com Tracing route to google.com [74.125.45.100]over a maximum of 30 hops:  0  bc [192.168.1.2]  1  router.home.lan [192.168.1.1]  2  ks-76-7-1-1.sta.embarqhsd.net [76.7.1.1]  3  ks-76-7-255-209.sta.embarqhsd.net [76.7.255.209]  4  ge-6-6.car2.StLouis1.Level3.net [4.53.162.97]  5  ae-4-4.ebr2.Chicago1.Level3.net [4.69.132.190]  6  ae-5.ebr2.Chicago2.Level3.net [4.69.140.194]  7  ae-2-2.ebr2.Washington1.Level3.net [4.69.132.70]  8  ae-92-92.csw4.Washington1.Level3.net [4.69.134.158]  9  ae-4-99.edge1.Washington1.Level3.net [4.68.17.208] 10  GOOGLE-INC.edge1.Washington1.Level3.net [4.79.22.38] 11  209.85.241.50 12  216.239.48.69 13  72.14.232.215 14  209.85.253.137 15  yx-in-f100.1e100.net [74.125.45.100] Computing statistics for 375 seconds...            Source to Here   This Node/LinkHop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address  0                                           bc [192.168.1.2]                                0/ 100 =  0%   |  1    0ms     0/ 100 =  0%     0/ 100 =  0%  router.home.lan [192.168.1.1]                                0/ 100 =  0%   |  2    7ms     0/ 100 =  0%     0/ 100 =  0%  ks-76-7-1-1.sta.embarqhsd.net [76.7.1.1]                                0/ 100 =  0%   |  3    7ms     0/ 100 =  0%     0/ 100 =  0%  ks-76-7-255-209.sta.embarqhsd.net[76.7.255.209]                                0/ 100 =  0%   |  4   23ms     0/ 100 =  0%     0/ 100 =  0%  ge-6-6.car2.StLouis1.Level3.net [4.53.162.97]                                0/ 100 =  0%   |  5   23ms     0/ 100 =  0%     0/ 100 =  0%  ae-4-4.ebr2.Chicago1.Level3.net [4.69.132.190]                                0/ 100 =  0%   |  6   20ms     0/ 100 =  0%     0/ 100 =  0%  ae-5.ebr2.Chicago2.Level3.net [4.69.140.194]                                0/ 100 =  0%   |  7   37ms     0/ 100 =  0%     0/ 100 =  0%  ae-2-2.ebr2.Washington1.Level3.net [4.69.132.70]                                0/ 100 =  0%   |  8   43ms     0/ 100 =  0%     0/ 100 =  0%  ae-92-92.csw4.Washington1.Level3.net [4.69.134.158]                                0/ 100 =  0%   |  9  ---     100/ 100 =100%   100/ 100 =100%  ae-4-99.edge1.Washington1.Level3.net [4.68.17.208]                                0/ 100 =  0%   | 10  ---     100/ 100 =100%   100/ 100 =100%  GOOGLE-INC.edge1.Washington1.Level3.net [4.79.22.38]                                0/ 100 =  0%   | 11   43ms     0/ 100 =  0%     0/ 100 =  0%  209.85.241.50                                0/ 100 =  0%   | 12   43ms     0/ 100 =  0%     0/ 100 =  0%  216.239.48.69                                0/ 100 =  0%   | 13   42ms     0/ 100 =  0%     0/ 100 =  0%  72.14.232.215                                0/ 100 =  0%   | 14   45ms     0/ 100 =  0%     0/ 100 =  0%  209.85.253.137                                0/ 100 =  0%   | 15   47ms     0/ 100 =  0%     0/ 100 =  0%  yx-in-f100.1e100.net [74.125.45.100] Trace complete.

We need to know where EXACTLY the packet loss originates from and to see if the packet loss continues on down stream from the problem hop.

--
--bc

Re: Packet loss to the west coast, ping spikes to the east

Sat, 07 Nov 2009 12:42:06 EDT

darcon posted : It's all my fault.

I should just bow dow and bend over, accepting it from our internet overlords.

When a paying customer is unable to do anything about something like this, the overwhelming feeling of helplessness and hostility is just rage-inducing.

Being able to have a steady internect connection and play, communicate, and interact with others across the nation is one of the few things that I can truly enjoy in this world, and when it is hindered by the complete uncaring of a corperation, something needs to be said, however harsh it may be.

Unfortunately this really is the only place where a halfway competent answer can be found with an issue like this, and when this place fails as well, it is just overwhelming.

Re: Packet loss to the west coast, ping spikes to the east

Sat, 07 Nov 2009 10:22:27 EDT

Go Tarheels posted : In other news, Hazy Arc is seeing first hop pings of 8ms whilst exploding the brains of N00bs with his Barrett .50 caliber Rifle on COD4.

Hazy Arc, do tell of your experience a year ago and the troubles that I went through to fix it!

Re: Packet loss to the west coast, ping spikes to the east

Fri, 06 Nov 2009 16:32:38 EDT

darcon posted : Seriously? There is NOTHING Embarq/CenturyLink can do about this?

»/linequality/nil/2583431

This is ridiculous.

Re: Packet loss to the west coast, ping spikes to the east

Fri, 30 Oct 2009 15:41:22 EDT

Hazy Arc posted : Yeah you definitely have some line issues going on. Send your phone number to CTL_Joey and he can check out your situation.

Re: Packet loss to the west coast, ping spikes to the east

Fri, 30 Oct 2009 15:39:11 EDT

darcon posted : I decided to do a tracert, now my first two hops are completely messed up, when just last night they were always under 8 ms.

Tracing route to www.l.google.com [74.125.45.103]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms DD-WRT [192.168.1.1]
2 129 ms 147 ms 53 ms tn-76-7-96-1.dhcp.embarqhsd.net [76.7.96.1]
3 177 ms 133 ms 133 ms tn-76-5-159-225.sta.embarqhsd.net [76.5.159.225]

4 70 ms 107 ms 67 ms sl-gw28-atl-11-3-0.sprintlink.net [160.81.212.29
]
5 136 ms 147 ms 147 ms sl-crs1-atl-0-12-0-3.sprintlink.net [144.232.5.1
49]
6 107 ms 98 ms 160 ms sl-crs1-dc-0-4-0-1.sprintlink.net [144.232.8.147
]
7 170 ms 77 ms 210 ms sl-st30-ash-0-2-0-0.sprintlink.net [144.232.25.1
3]
8 117 ms 139 ms 157 ms sl-googl11-219203-0.sprintlink.net [144.228.205.
18]
9 142 ms 199 ms 133 ms 216.239.48.108
10 148 ms 186 ms 67 ms 66.249.95.149
11 67 ms 37 ms 222 ms 209.85.254.241
12 44 ms 139 ms 180 ms 209.85.253.137
13 172 ms 46 ms 53 ms yx-in-f103.1e100.net [74.125.45.103]

Trace complete.

This town is so goddamned depressing.

Re: Packet loss to the west coast, ping spikes to the east

Fri, 30 Oct 2009 15:33:23 EDT

darcon posted : Alright, I've got a smokeping running for 24 hours.

»/r3/smokeping.···153fdb44

Man...my Embarq DSL experience started so good...now it's going downhill fast :huh:

Re: Packet loss to the west coast, ping spikes to the east

Fri, 30 Oct 2009 14:45:46 EDT

Hazy Arc posted : »/smokeping

Sign up for a smokeping and post your graph here.

Re: Packet loss to the west coast?

Fri, 30 Oct 2009 14:37:17 EDT

darcon posted : *sigh*

It's gotten worse overnight:

»/linequality/nil/2581010

I can't win for losing with the internet in this shitty town, it seems.

Packet loss to the west coast, ping spikes to the east

Thu, 29 Oct 2009 20:49:14 EDT

darcon posted : Hey, I just recently got Embarq, and I must say it is a vast improvement in stability over Charter here.

Unfortunately, lately it seems I've been having some bad packet loss to anywhere out of the Eastern US (I live in Johnson City, TN). This is most notable during gaming sessions. Here are a couple of recent line quality tests:

»/linequality/nil/2580734

»/linequality/nil/2580754

Any feedback would be appreciated.