dslreports logo
    All Forums Hot Topics Gallery


how-to block ads

Search Topic:
share rss forum feed


Henniker, NH
reply to exeter

Fairpoint 30/15

Experienced Same Slowdown Here in Kittery, Maine.We go through Portsmouth Hub. Support Stated it was My Router. So After the Weekend They Got Me Another Router.

We Shall See.
Time Will Tell If They Can Provide Service To The Wires.
They Should Have Never Been Approved by the States in Northern New England.......


reply to exeter

Re: [speed/latency] Speeds slow on 30/15 connection NH/ME

Just about 12PM, 15/2 package:


reply to exeter
Alter.net is Verizon... I guess they were Fairpoints main transit provider and now it looks like they're using Cogent and some others.

Weird that it took that long to get fixed! lol


How could I trace the route ?

Milford, NH
·FirstLight Fiber
·Hollis Hosting
·G4 Communications

1 edit
said by captcaper :

How could I trace the route ?

Assuming you are using Windows go to the command prompt.

Type: tracert (the site you want to traceroute to)

fixed HTML formatting


reply to xsbell
FairPoint totally fucked up (pardon the language) by going with Cogentco transit.

I ping 145ms to the town right next to me, but ping 25 to Boston (it used to be 5ms to Manchester, 10ms to Boston on Alter.net).

Any connections made outside of the general Northeastern New England area results in extremely poor performance.

On alter.net, used to get 85ms to Europe servers. Now? 350ms+ to Europe.

Used to do 30ms to California from NH, now it's 100ms+ and download speed is literally cut by 90%.


Nashua, NH
reply to anon1
This has nothing to do with DNS. Why are you posting on this thread?


You must be lost mrmengo, nobody here is discussing DNS?


Nashua, NH
reply to exeter
Don't know why I thought that this would have changed by now. The routing is still the same. Fiber still does not act like fiber. Same song and dance. What faripont is doing is wrong. Same ping times when most want to use their service at home.

The following is from 9am 4/7/2012
tracert www.google.com

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

1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home []
2 4 ms 4 ms 4 ms
3 4 ms 4 ms 4 ms
4 8 ms 6 ms 6 ms POS3-0-0.GW3.BOS4.ALTER.NET []
5 9 ms 11 ms 9 ms 0.so-0-1-2.XL3.BOS4.ALTER.NET []
6 15 ms 14 ms 14 ms 0.xe-6-1-2.XT1.NYC4.ALTER.NET []
7 15 ms 19 ms 14 ms TenGigE0-4-2-0.GW8.NYC5.ALTER.NET []

8 63 ms 64 ms 64 ms google-gw.customer.alter.net []
9 14 ms 16 ms 24 ms
10 17 ms 14 ms 21 ms
11 44 ms 24 ms 24 ms
12 31 ms 34 ms 31 ms
13 43 ms 44 ms 41 ms
14 * * * Request timed out.
15 35 ms 34 ms 34 ms vb-in-f106.1e100.net []

Trace complete.


Not sure what in the world is going on. Spent pretty much the entire morning yesterday routing through Cogent, then late evening the routing has returned back to Alter.net and has been so since.


reply to exeter
airpoints High-speed internet service. But I am having major speed/latency problems (2.13 D, .32 U, 76 P)as well as total loss of service time and time again here in southern Vermont. Fairpoint tech support claims they are working on it, but the problematic speed/latency issues continue with test reading results all over the place. They will sometimes credit my account a few dollars to try to appease me. But, I need reliable internet service. Anyone know of any other internet service providers for the southern Vermont, West Wardsboro area?


More issues today 4/11/12.....

- Cant load web pages, this barely loaded after 5 tries.
- Traceroutes not completing or even coming close.


Derry, NH
Same here, some will load, others will not. wondering if its a dns issue out there somewhere.... who knows :/


Doesnt look like dns to me. Looks like routing problems at fairpoint.


reply to Desmoe
Located in Nashua. Having same issue today! Thought everything was resolved. Trace route not finishing. Or when it does only routing thru alter.net. Thank goodness for iPhone & 3G! But seriously we love FIOS/FAST bur come Fairpoint! A permanent fix would be nice!

Kirby Smith

Derry, NH
·Fairpoint Commun..
From Derry NH

Pings to various DNS servers (Fairpoint's, OpenDNS', Google's, and Level3's) work when using their IP address; some diverse websites are just as fast as usual, e.g., dslreports.com, animesuki.com. Cnn.com presents text but not pictures. foxnews.com times out, can't be pinged, and their akamai servers can't be pinged. Ubuntuforums can't be reached. ChinaPost Taiwan can be reached. NHKWorld Japan can be reached. Whois to various sites performing whois service variously claim foxnews.com can't be reached or doesn't exist. This is certainly unusual.

Partial DNS poisoning?



The reason some sites only have text but not pictures is their graphic content may be hosted on another provider (eg. akamai) while text comes straight through. Our routing appears to be broken at the moment to half of the internet as far as I can tell


reply to exeter
30/15 Portsmouth NH. For the most part, I get the advertised speed. However, the responsiveness and reliability is just not there. I have to refresh webpages throughout the day, VoIP calls drop, and according to the DSLreports line monitoring, I've had more packet loss than normal.

Throughput is only part of the story folks. I believe the problem lays with whoever FairPoint is using as a backbone service provider. Internally, tracerouts and connectivity with discoverable routers seems stable and quick. Things get funky when passing over to alter.net, above.net, etc.

Keep in mind, that FairPoint has implemented substantial changes with their infrastructure, as well as with their backbone provider in the past few months. Things are better, but not Comcast reliable (sounds odd saying that).


reply to exeter
Since FairPoint picked up Cogentco as one of the backhaul transit providers, everytime my transit ends up running through Cogentco my latency is absolutely destroyed.

The same applies with Above.net

In games where the server is located in New York:

Going through Alter.net -> 12ms ping
Above.net -> 45ms
Cogentco -> 350+ms


reply to exeter
Correction on my previous post, Above.net should red 145ms, not 45ms.