syoder
join:2008-02-11
Syracuse, IN
1 edit | reply to syoder
Re: Embarq network congestion, latency and packet loss in IN
Now the latency is occuring on the Sprintlink handoff. They seem to be messing with routing as well.
Matt's traceroute [v0.42]
Scott-Home Sat Jun 1 14:31:22 2002
Keys: D - Display mode R - Restart statistics Q - Quit
Packets Pings
Hostname %Loss Rcv Snt Last Best Avg Worst
1. oh-71-1-32-1.dhcp.embarqhsd.net 0% 7 7 11 6 10 15
2. oh-71-0-195-249.sta.embarqhsd.net 0% 7 7 28 26 29 33
3. sl-gw31-chi-4-1.sprintlink.net 0% 7 7 353 328 337 353
4. sl-bb21-chi-4-0.sprintlink.net 0% 7 7 349 326 338 349
5. sl-bb22-chi-15-0.sprintlink.net 0% 7 7 346 327 370 496
6. sl-st21-chi-13-0-0.sprintlink.net 0% 7 7 352 326 337 352
7. 144.223.241.54 0% 6 7 341 327 334 341
8. 216.239.48.154 0% 6 7 336 328 332 336
9. 72.14.232.57 0% 6 7 342 328 338 359
10. 64.233.175.42 0% 6 6 340 329 338 345
11. py-in-f104.google.com 0% 6 6 344 328 337 344
And from QWest inbound:
Looking Glass
Traceroute to 71.1.32.1 from atl-engr-01.inet.qwest.net
--------------------------------------------------------------------------------
traceroute to 71.1.32.1 (71.1.32.1), 30 hops max, 40 byte packets
1 atl-svcs-01 (205.171.21.214) 0.800 ms 0.405 ms 0.399 ms
2 atl-core-02 (205.171.21.17) 0.499 ms 0.473 ms 0.464 ms
3 atl-brdr-04 (205.171.21.169) 0.415 ms 0.356 ms 0.350 ms
4 sl-bb23-atl-10-3.sprintlink.net (144.232.9.85) 0.842 ms 0.685 ms 0.665 ms
5 sl-bb21-atl-8-0.sprintlink.net (144.232.12.25) 0.941 ms 0.874 ms 0.744 ms
6 sl-crs1-atl-0-4-0-3.sprintlink.net (144.232.12.148) 1.104 ms 0.820 ms 0.787 ms
7 sl-crs1-chi-0-12-3-0.sprintlink.net (144.232.19.89) 16.182 ms 16.247 ms 15.828 ms
8 sl-bb22-chi-13-0.sprintlink.net (144.232.26.49) 15.879 ms 15.860 ms 15.864 ms
9 sl-bb20-roa-8-0-0.sprintlink.net (144.232.18.37) 18.919 ms 18.918 ms 18.915 ms
10 sl-gw10-roa-9-0.sprintlink.net (144.232.0.6) 18.995 ms 19.317 ms 19.098 ms
11 sl-sprintwrbm-27-0.sprintlink.net (160.81.95.38) 339.747 ms 344.953 ms 342.997 ms
12 oh-71-1-32-1.dhcp.embarqhsd.net (71.1.32.1) 358.928 ms 359.873 ms 352.231 ms
|
|
userequal
join:2007-04-03
Lapel, IN
| reply to Gardman
Never even got fixed for Lapel. I worked from home today (through remote desktop), and it was fine until around 3pm. So something isn't able to handle the evening load. I think all of Lapel gets routed up North that's why our first Embarq hop is so high. Lowest I've seen is around 32ms on fast channel. |
|
syoder
join:2008-02-11
Syracuse, IN | Actually your first hop is high becuase you don't have FastPath enabled. The data being transmitted on your ADSL link is being interleaved to allow for error correction but at the cost of about 30 ms of added latency. |
|
userequal
join:2007-04-03
Lapel, IN | No, I'm on fast channel. Interleave is much higher. |
|
syoder
join:2008-02-11
Syracuse, IN | So you saw your latency drop immediately after they enabled FastPath?
They switched me while I was on the phone with a tech and my latency went from 40 ms down to 7 ms immediately. |
|
userequal
join:2007-04-03
Lapel, IN | Yea , it dropped around 30 ms. Your lucky, you're closer to where they have you routed. I'd love to have a single digit first Embarq hop. |
|
maximus1969
@embarqhsd.net
| reply to syoder
not real sure what you guys are talking about with hops and latency..I just know my conn is crap here in Lapel, It was fine until last Friday and its been horrible ever since, no x box and ps3 online gaming...I'm getting very upset and to my knowledge no one at Embarq has addressed this with a problem and a fix date? have they?
I went up to the next package available from 3000 d/l 500 up to 5000 d/l and 768? up...didnt really help...please fix this crap |
|
syoder
join:2008-02-11
Syracuse, IN
1 edit | You guys in Lapel might have a different issue between your DSLAM and the RedBack. Your traceroutes show high latency on the first hop. If your router (not your PC) shows 0% in and out usage during your traceroute then you can pretty safely conclude the problem is with Embarq and not due to your link being congested. As I recall all of our traffic goes to Roachdale, IN where it's handed off to Sprintlink. Perhaps the problem is at Roachdale which is close enough to you guys to be your first hop.
The rest of us have had a problem with latency occuring between routers 2 hops into the network.
It got a lot better Monday afternoon and I actually saw latency of 85 ms in WoW for a little bit Monday evening whereas it's normally 180-250 ms. But as of now it's 850 ms in WoW which is going to make raiding impossible. |
|
lordlitwicki
join:2006-10-05
Plymouth, IN
| I'm having the exact same issue here in Plymouth syoder. Connection was the fastest it ever was on Monday afternoon and worked great until today around 1PM when it slowed wayyyyyyy down again. I called Embarq and they told me all of the issues they were having with the redback in Indiana have been fixed, and I explained it was fixed but the issue is back. He assured me it's on my end and blamed my router. This is bull it's not my router when everyone seems to be having the problem. I'm going to cal them again tonight when i get home. |
|
latent
@embarqhsd.net
| reply to syoder
We've been having intermittent problems for a week or so in NW IN but today the connection is as bad as it has ever been. The ICMP responses don't reflect the severity of the packet loss going on. It might as well be a 5k+ ping (worse than satellite) in software where response time matters and only has ~4.2 kb/s of bandwidth at the moment (worse than dialup). They've been quick to resolve this kind of situation before but it seems to be getting progressively worse...
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 11 ms 11 ms 11 ms oh-71-50-192-1.dhcp.embarqhsd.net [71.50.192.1]
3 28 ms 29 ms 29 ms crohmnfd02 [69.69.33.245]
4 361 ms 336 ms 349 ms sl-gw4-roa-0-1.sprintlink.net [144.232.196.41]
5 353 ms 354 ms 354 ms sl-bb22-roa-2-1.sprintlink.net [144.232.17.205]
6 362 ms 363 ms 366 ms sl-bb20-akr-5-0-0.sprintlink.net [144.232.18.110
]
7 * * 376 ms sl-bb27-rly-1-0-0.sprintlink.net [144.232.9.216]
8 * 374 ms 375 ms sl-bb23-rly-13-0.sprintlink.net [144.232.14.141]
9 373 ms 376 ms 382 ms sl-bb24-rly-10-0.sprintlink.net [144.232.14.130]
10 383 ms 385 ms 381 ms sl-st22-ash-5-0.sprintlink.net [144.232.20.155]
11 * 374 ms 372 ms sl-tisca1-3-0.sprintlink.net [144.223.246.30]
12 * * 382 ms so-1-0-0.nyc22.ip.tiscali.net [213.200.80.125]
13 370 ms 381 ms 386 ms netaccess-gw.ip.tiscali.net [213.200.73.122]
14 386 ms 393 ms 391 ms 0.e1-4.tbr2.mmu.nac.net [209.123.10.77]
15 378 ms 386 ms * 0.e-1-1.tbr2.oct.nac.net [209.123.10.21]
16 384 ms 392 ms 383 ms 0.e-1-3.tbr1.oct.nac.net [209.123.10.45]
17 391 ms * 392 ms 0.ge-1-2-0.gbr1.oct.nac.net [209.123.10.58]
18 * 391 ms * www.dslreports.com [209.123.109.175]
19 381 ms 386 ms 384 ms www.dslreports.com [209.123.109.175]
Trace complete. |
|
ALPHAxDOG
Premium
join:2007-10-09
Rising Sun, IN
| 
WEEEEEEEEEEEEEE |
 |
|
userequal
join:2007-04-03
Lapel, IN
| reply to latent
Currently mine isn't as bad. |
|
Stactik
@embarqhsd.net
|  reply to syoder
Yet another day goes by and my ping continues to be horrible.. here's a screenshot of it tonight...
GG Embarq, way to make us pay for somthing that's been pretty unreliable as of late
- Remington, Indiana |
|
Supervisor
Premium
join:2006-03-26
Lebanon, PA
| reply to latent
Embarq network congestion, latency and packet loss in PA
 Mine is also crapping out at the Embarq connection between Sprintlink at Mansfield Ohio (crohmnfd). I remember something similar happening last year at the same spot. It was frustrating talking to techs & admins on both the Embarq & Sprintlink side of the connection. Embarq blamed Sprintlink and Sprintlink blamed Embarq. For the past month or two its been bogging down around 300ms or so during early evening, but was still usable. This evening it's practically useless:
1 me (192.168.1.1) 4.138 ms 0.906 ms 1.328 ms
2 oh-69-34-XXX-XXX.sta.embarqhsd.net (69.34.XXX.XXX) 10.301 ms 9.675 ms 8.823 ms
3 crohmnfd02.embarqhsd.net (69.68.43.245) 36.666 ms 34.425 ms 34.140 ms
4 sl-gw10-roa-3-3.sprintlink.net (160.81.95.37) 789.292 ms 779.419 ms 771.294 ms
5 sl-bb20-roa-2-0.sprintlink.net (144.232.0.5) 816.273 ms 809.015 ms 857.364 ms
6 sl-bb22-chi-4-0-0.sprintlink.net (144.232.18.36) 786.916 ms 798.740 ms 794.661 ms
Too bad there's no choice in DSL providers in most areas. |
|
ALPHAxDOG
Premium
join:2007-10-09
Rising Sun, IN | reply to Stactik
Re: Embarq network congestion, latency and packet loss in IN
Here are the Speedtest:
Last Result:
Download Speed: 198 kbps (24.8 KB/sec transfer rate)
Upload Speed: 47 kbps (5.9 KB/sec transfer rate) |
|
Stactik
@embarqhsd.net
| reply to syoder
Just talked to a representative, and this is what i was told...
Heather T. - Unfortunately we are having trouble with speeds in your area, the engineers are working on it. We hope to have it resolved within 24-48 hours but I have not been given an 'official' time it will be fixed. You are welcome to come back to chat for updates though, it was allegedly fixed for a while and has returned, I am really sorry about that!
Area: 47977 (Remington, Indiana) |
|
JimMc
@embarqhsd.net
| reply to Supervisor
Ohio feels your pain
I'm in Marysville, Ohio, and I've been having the same problems as y'all lately. Pingplotter jumps from 72 to 797 avg between Embarq and Sprint.
Ridiculous. The automated message over Embarq phone support said at approx. 5:00 today that there would be a fix within 24 hours. Of course, that message has probably been up for 24 hours, who knows. |
|
ALPHAxDOG
Premium
join:2007-10-09
Rising Sun, IN
| reply to Stactik
Re: Embarq network congestion, latency and packet loss in IN
Packet_Loss |
|
|
Stactik
join:2008-02-20
Remington, IN | reply to syoder
Dont you just love those automated responses? lol... that's why i use the www.myembarq.com/contact_us.php page |
|
RadioOp
@embarqhsd.net
| reply to syoder
Back to the same crap here in Decatur IN. Noticed it this afternoon at the office (We use Embarq there too). Got home tonight and it is as worse as ever. So bad that I can't even do a speedtest, the sites won't load all of the way. This is absolutely terrible!!!
Tracing route to google.com [64.233.167.99]
over a maximum of 30 hops:
1 1 ms 1 ms 18 ms 192.168.0.1
2 28 ms 27 ms 27 ms oh-76-2-80-1.dhcp.embarqhsd.net [76.2.80.1]
3 45 ms 45 ms 46 ms oh-71-0-6-61.sta.embarqhsd.net [71.0.6.61]
4 153 ms 152 ms 152 ms sl-gw31-chi-4-1.sprintlink.net [160.81.42.5]
5 153 ms 153 ms 153 ms sl-bb21-chi-4-0.sprintlink.net [144.232.26.29]
6 152 ms 153 ms 149 ms sl-bb22-chi-15-0.sprintlink.net [144.232.26.97]
7 151 ms 154 ms 152 ms sl-st21-chi-11-0-0.sprintlink.net [144.232.20.21
]
8 154 ms * 153 ms 144.223.241.54
9 * 152 ms 153 ms 209.85.250.237
10 155 ms 157 ms 155 ms 72.14.232.53
11 155 ms 162 ms 163 ms 64.233.175.26
12 * 157 ms 155 ms py-in-f99.google.com [64.233.167.99]
Trace complete. |
|
