dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
3863
share rss forum feed

amh1

join:2013-01-07
Salem, NH

1 edit

Any FP DSL users in Southern NH experiencing uplink probs?

Hi, I am a Fairpoint user in southern NH. For about a week I have been experiencing very poky internet access. After getting annoyed enough to start doubting the connection, I did some speedtest runs and found out that I have what appears to be slow uplink bandwidth. On what is theoreticaly a 3.3/0.8 Mb link I am benchmarking a relatively consistent 2.6-2.9Mb downlink and an erratic uplink measuring anywhere from a few kb to 300kb (mostly around 100kb or 0.1Mb/sec); it used to be a solid 600-700kb before this snafu.

I checked the Westell 6100 model xvr stats, here is what I saw:
Transceiver Information Down Stream Path /Up Stream Path
DSL Speed (Kbits/Sec) 3360 /864
Margin (dB) 27.5 /9.0
Line Attenuation (dB) 28.8 /11.5
Transmit Power (dBm) 6.6 /11.9

Sorry for the long background info.

Anyone in Southern NH seeing recent upload bottlenecks? And if not, what are the xvr stats?

Thx,
AMH


storm58

join:2007-11-01
I'm in southwestern NH (Monadnock region) and the speeds have been really solid. Your line Attenuation and Margin look really good! Your DL & UL speed are provisioned a little lower than mine. Here's a link about the stats... »AT&T Southeast Forum FAQ »How do I access the Westell line stats and logs? What do the numbers mean?


amh1

join:2013-01-07
Salem, NH
Thx storm58. I should have been more specific about my S. NH area of interest, it is Windham/Derry area as I suspect this problem, if not my equipment related, may be CO specific. I agree with your assessment of the line attenuations and receive SNR, the xmit SNR though a tad on the low side should not be causing such a low upload speed.

I have tried calling customer service, unfortunately they say no one else is reporting problems, works just fine here and walk me through a litany of useless acct questions and scripted debug calisthenics. Wish there was an easy way to tier-2 support with these guys.

»www.speedtest.net/result/2423287784.png


tschmidt
Premium,MVM
join:2000-11-12
Milford, NH
kudos:9
Reviews:
·Hollis Hosting
·G4 Communications
reply to amh1
Since modem stats look OK problem is not the physical DSL circuit. It is unusual for upload speed to be so poor and still have good download speed.

1) Make sure nothing on your LAN or PC is uploading when you run the speed test. If possible disconnect everything and try another computer.

2) Try running traceroute (tracert in Windows) to stable sites like this one. Latency should slowly increase with hop count and distance. At your speed first hop latency should be about 25ms.

/tom

amh1

join:2013-01-07
Salem, NH
I have done that; more than one device sees slow uplink, no devices are continuously uploading and when I isolate router/network from FP and hardwire PC to DSL modem directly I continue to see same slow uploink behavior.

When I connect my PC to a different broadband connecttions I get faster uploads.

Thx,
AMH
PS I thought 9db uplink SNR is only fair


tschmidt
Premium,MVM
join:2000-11-12
Milford, NH
kudos:9
Reviews:
·Hollis Hosting
·G4 Communications
said by amh1:

PS I thought 9db uplink SNR is only fair

The more the better but 9 dB is not too bad for upload.

/tom

DrSmith

join:2009-02-16
united state
reply to amh1
Ouchie! I'm seeing unusually poor upload speeds today. I pay for slow DSL to begin with 768k/128k, but I've never seen it this bad.

DrSmith

join:2009-02-16
united state
reply to amh1
okay, here's a slightly better result, but still only getting about 50% of my advertised upload speed. I am also in the Windham/Derry area.

amh1

join:2013-01-07
Salem, NH
Hi DrSmith,
Thanks for the confirmation, it does appear that the FP Derry NH CO (which serves Windham) is having issues. FP opened a ticked and said will investigate the slow uplink, have not heard back yet from the tech, service continues to be miserably slow.
Hope you called FP as well.
AMH

DrSmith

join:2009-02-16
united state
said by amh1:

Hope you called FP as well.

Not yet. I can't stomach the labyrinth required to reach real support either. Plus I have to disconnect my WiFi and directly connect a PC to my Westell 6100 before calling, otherwise the flow chart is even longer.

DrSmith

join:2009-02-16
united state
reply to amh1
Woo hoo! Made it through the maze, actually not too bad. And repair ticket is now open for "poor upload speed"


tschmidt
Premium,MVM
join:2000-11-12
Milford, NH
kudos:9
Good the hear - be interesting to see what they find out.

My want to do traceroute to this site and see if anything unusual jumps out.

BTW you have IM from me from our previous exchange several weeks ago.

/tom

amh1

join:2013-01-07
Salem, NH
Hi Tom,
What site would you recommend tracerouting to? I do not know what the ip address of the Derry FP CO is.

If this persists (it's been ~1wk now) it maybe worth calling G4 and ask if they have equipment in the Derry CO.

AMH


tschmidt
Premium,MVM
join:2000-11-12
Milford, NH
kudos:9
Reviews:
·Hollis Hosting
·G4 Communications
said by amh1:

What site would you recommend tracerouting to?

I like using dslreports.com - server is in NY so it is a good overall test without getting into distance issues.

/tom

amh1

join:2013-01-07
Salem, NH
Here is Westell 6100 diagnostic tracerout for dslreports.com
--- Trace Route Test Results ---
1 10.20.6.1 (10.20.6.1) 45.175 ms 6.326 ms 5.900 ms
2 64.222.166.165 (64.222.166.165) 5.323 ms 6.103 ms 5.884 ms
3 pool-64-222-213-132.port.east.myfairpoint.net (64.222.213.132) 10.547 ms 10.503 ms 10.833 ms
4 xe-1-2-0.mpr4.bos2.us.above.net (64.125.71.169) 13.965 ms 13.988 ms 13.750 ms
5 xe-4-2-0.cr2.dca2.us.above.net (64.125.29.34) 24.820 ms 24.913 ms 46.304 ms
6 xe-0-0-0.cr1.dca2.us.above.net (64.125.28.241) 24.854 ms 25.516 ms 26.755 ms
7 xe-1-0-1.er1.iad10.us.above.net (64.125.26.238) 58.070 ms 25.045 ms 25.345 ms


tschmidt
Premium,MVM
join:2000-11-12
Milford, NH
kudos:9
Reviews:
·Hollis Hosting
·G4 Communications
said by amh1:

Here is Westell 6100 diagnostic tracerout for dslreports.com

I think you cut off part of the traceroute. Did you capture the info when speed was OK or when uplink was horrible?

Try to run it a few more times for consistency. An occasional modest spike is not all that big a deal.

First hop looks good at only 6ms, I guess you are on Fastpath, but noticed it spikes to 45ms. Keep in mind 1st hop encompass a lot since from customer to edge router traffic is carried over ATM so invisible to traceroute.

/tom

amh1

join:2013-01-07
Salem, NH

1 edit
Hi Tom, you are correct - bad cut and paste, clipped end of log - here are three retries.
Nothing egregious, the problem has to be higher up the comms stack.
--- Trace Route Test Results ---
1 10.20.6.1 (10.20.6.1) 5.874 ms 6.353 ms *
2 64.222.166.167 (64.222.166.167) 7.507 ms 7.524 ms 7.801 ms
3 burl-lnk-70-109-168-138.ngn.east.myfairpoint.net (70.109.168.138) 12.252 ms 12.139 ms 12.056 ms
4 te8-5.ccr01.alb02.atlas.cogentco.com (38.104.52.29) 18.889 ms 16.991 ms 17.247 ms
5 te9-7.ccr01.jfk01.atlas.cogentco.com (154.54.43.6) 21.133 ms 20.183 ms 20.673 ms
6 te4-1.ccr01.ewr02.atlas.cogentco.com (154.54.3.209) 20.358 ms 21.370 ms 20.187 ms
7 te2-3.ccr01.ewr05.atlas.cogentco.com (154.54.47.162) 22.105 ms 20.800 ms 20.932 ms
8 38.122.158.2 (38.122.158.2) 24.987 ms 20.165 ms 21.357 ms
9 * 0.e1-4.tbr2.oct.nac.net (209.123.10.126) 22.411 ms 23.370 ms
10 vlan808.esd1.oct.nac.net (209.123.10.42) 24.314 ms 23.423 ms 21.642 ms
11 * www.dslreports.com (209.123.109.175) 21.108 ms 21.536 ms
--- Trace Route Test Results ---
1 10.20.6.1 (10.20.6.1) 5.874 ms 6.353 ms *
2 64.222.166.167 (64.222.166.167) 7.507 ms 7.524 ms 7.801 ms
3 burl-lnk-70-109-168-138.ngn.east.myfairpoint.net (70.109.168.138) 12.252 ms 12.139 ms 12.056 ms
4 te8-5.ccr01.alb02.atlas.cogentco.com (38.104.52.29) 18.889 ms 16.991 ms 17.247 ms
5 te9-7.ccr01.jfk01.atlas.cogentco.com (154.54.43.6) 21.133 ms 20.183 ms 20.673 ms
6 te4-1.ccr01.ewr02.atlas.cogentco.com (154.54.3.209) 20.358 ms 21.370 ms 20.187 ms
7 te2-3.ccr01.ewr05.atlas.cogentco.com (154.54.47.162) 22.105 ms 20.800 ms 20.932 ms
8 38.122.158.2 (38.122.158.2) 24.987 ms 20.165 ms 21.357 ms
9 * 0.e1-4.tbr2.oct.nac.net (209.123.10.126) 22.411 ms 23.370 ms
10 vlan808.esd1.oct.nac.net (209.123.10.42) 24.314 ms 23.423 ms 21.642 ms
11 * www.dslreports.com (209.123.109.175) 21.108 ms 21.536 ms
--- Trace Route Test Results ---
1 10.20.6.1 (10.20.6.1) 6.467 ms 5.686 ms 5.915 ms
2 64.222.166.167 (64.222.166.167) 7.797 ms 9.245 ms 6.829 ms
3 burl-lnk-70-109-168-138.ngn.east.myfairpoint.net (70.109.168.138) 13.472 ms 12.004 ms 15.766 ms
4 te8-5.ccr01.alb02.atlas.cogentco.com (38.104.52.29) 17.165 ms 16.837 ms 20.052 ms
5 te9-7.ccr01.jfk01.atlas.cogentco.com (154.54.43.6) 20.621 ms 20.402 ms 21.227 ms
6 te4-1.ccr01.ewr02.atlas.cogentco.com (154.54.3.209) 21.300 ms 20.145 ms 24.011 ms
7 te2-3.ccr01.ewr05.atlas.cogentco.com (154.54.47.162) 21.701 ms 22.112 ms 24.113 ms
8 38.122.158.2 (38.122.158.2) 21.613 ms 22.308 ms 55.900 ms
9 0.e1-4.tbr2.oct.nac.net (209.123.10.126) 23.355 ms 21.565 ms 21.423 ms
10 vlan808.esd1.oct.nac.net (209.123.10.42) 24.303 ms 21.743 ms 21.669 ms
11 www.dslreports.com (209.123.109.175) 23.585 ms 21.739 ms 21.201 ms

amh1

join:2013-01-07
Salem, NH
Tonight, it is fixed. After opening a ticket, looks like one of their techs fixed whatever was logjaming the uplink.
Here is the new speedtest.net benchmark: »www.speedtest.net/result/2425610571.png after all this, a C grade!

Though happy things are back to normal, I am a bit annoyed with this event and hoping for a better broadband solution soon. I am not a fan of Comcast’s great deals then back to "regular pricing for existing customers". I wish there was a broadband supplier offering a good 10-15Mb product with less sleaze than Comcast and more competence than Fairpoint.

Thanks to all for the technical and moral support.

Rgds,
AMH

DrSmith

join:2009-02-16
united state
reply to amh1
Hmm, still no joy here. And my traceroute has all the same hops, including the first. So I think our DSLs terminate in the same CO. At least we know they fix problems in the order they were reported


tschmidt
Premium,MVM
join:2000-11-12
Milford, NH
kudos:9
Reviews:
·Hollis Hosting
·G4 Communications
Click for full size
ADSL end-to-end
Too bad whatever FairPoint did for amh1 See Profile did not resolve your problem.

One point of explanation - ADSL is transported using ATM between customer premise and ISP edge router. Unfortunately this means the ATM path is invisible to TCP/IP. The ISP edge router is probably not located at the serving Central Office but rather at a network operations center. Given amh1 See Profile low latency to the edge router it cannot be too far away unless FairPoint has figured out how to exceed the speed of light.

Here is an old block diagram from Verizon, but I assume it is pretty generic so probably still applies to FairPoint.

The terminology can be a little confusing. Even though you are getting ADSL from FairPoint, there are two parts of FairPoint involved in delivering ADSL, The ILEC (incumbent local exchange carrier) provides the copper subscriber circuit. Since you are a FairPoint ADSL customer the DLEC (data local exchange carrier) is also FairPoint. Back in the days when third parity ISP's resold ADSL (not sure if anyone still does that) the DLEC was also FairPoint. In the case of collocation ISPs like G4 and Covad I'm not sure how much if any use they make of ILEC's DLEC service.

/tom

DrSmith

join:2009-02-16
united state

1 recommendation

All fixed! Just spoke with Gary at FP and he said I was on a congested T1 from Derry to Manchester. They switched me over to the alternate T1 and all is well. Don't see any T1's in your old network pic there Tom (maybe in the Cell Relay net?). And I thought ATM was 20 years old. Guess there's a T1 backhaul that is even older.

Also explains why AMH's fix did not also fix me. They've just oversubscribed a backhaul and wait for customers to complain before leveling out the traffic. Not the best policy, IMHO, but I cannot complain about the repair service once the problem was ticketed.

DrSmith

join:2009-02-16
united state
reply to tschmidt
//

amh1

join:2013-01-07
Salem, NH

1 recommendation

reply to tschmidt
Hi Tom,
Thanks for the diagram, it gives me a better understanding of how you got your BW upto 6Mb

FP did a truck roll and the tech came in a did some testing copper line measurement from inside and ourside of the house to the DSLAM.

He identified some wiring in my house that could be improved and after some quick re-wiring, my SNR and line attenuation are better.
Here are the new XVR stats:
Transceiver Information Down Stream Path/ Up Stream Path
DSL Speed (Kbits/Sec) 3360/ 864
Margin (dB) 28.8/ 17.0
Line Attenuation (dB) 19.1/ 8.0
Transmit Power (dBm) 5.8/ 11.9

here are the before re-wiring numbers restated for reference
DSL Speed (Kbits/Sec) 3360 /864
Margin (dB) 27.5 /9.0
Line Attenuation (dB) 28.8 /11.5
Transmit Power (dBm) 6.6 /11.9

Speedtest remains the same, a good ~3Mbps up, 0.7Mbps dn

It is worth noting that the uplink problem that got this thread started did not exist with the older/noisier wiring and that the fix last night was done without any rewiring - something upstream of the DSLAM. However I am glad the FP tech came and improved the SNR.

Rgds,
AMH