NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
 ·SONIC.NET
·Pacific Bell - SBC
| reply to again
Re: [speed/latency] speedtest bangor maine said by again :So GWI runs there own fiber from the CO, didn't know that.
It is fairly common for a CLEC to place their own DSLAM in a CO (old Federal regulations required it), and connect that DSLAM to their own network. Only the copper from the CO to the customer is owned by the ILEC. From the DSLAM back to the CLEC network is separate from the ILEC network.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
Reviews:
 ·RoadRunner Cable
·Fairpoint Commun..
| reply to rblenkhorn
It baffles me as to why you would purchase unFairpoint as your ISP when there are more options in Bangor. I pay 25/month and just did a speed test and got
Download: 27Mbps
Upload: .98Mbps
Ping: 44ms
And you did the test at 9:49am so I'd like to see a speed test between 4pm and 10pm. I bet that down speed will be way down.
I had unFairpoint and lived 1500ft from the CO and never got even close to advertised speeds. During the time you did your test I could sometimes get 2.3Mbps down but after 4pm no way. I couldn't even surpass 1Mbps. I love buffering. |
|
| Pray tell, who offers 27 mbps for $25 in Bangor. |
|
 JJW
@verizon.net | Im in NH, had VZ FIOS before fairpoint took over. Recently service has taken a huge dive. Major latency, my packets are routed via NYC peer, outside networks intermittently cant reach my IP space.
I guess my biggest grip is why do my packets go from NH,Boston to NYC then internet.
Are they saving money by grouping everyone in north east via same gateway/pop? Cause the service sucks now, i can handle a few spikes in latency but their current prb with their BGP routing is getting frustrating. ANyone with 3rd party VPN tunnels built to other ISPs must have the same prbs as me. |
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| said by JJW :I guess my biggest grip is why do my packets go from NH,Boston to NYC then internet.
Isn't your first IP hop "the Internet"? If not, where does "the Internet" begin?
05/31/11 13:24:36 Slow traceroute www.dslreports.com
Trace www.dslreports.com (209.123.109.175) ...
68.127.139.254 RTT: 9ms TTL: 64 (adsl-68-127-139-254.dsl.pltn13.pacbell.net ok)
99.36.71.130 RTT: 9ms TTL:254 (dist2-vlan52.pltnca.sbcglobal.net ok)
151.164.103.6 RTT: 9ms TTL:253 (ag2-10g0-12-5-0.pltnca.sbcglobal.net ok)
151.164.52.131 RTT: 10ms TTL:251 (ppp-151-164-52-131.rcsntx.swbell.net ok)
151.164.251.34 RTT: 12ms TTL:251 (asn4436-nlayer.pxpaca.sbcglobal.net fraudulent rDNS)
69.22.153.18 RTT: 11ms TTL:250 (ae0-70g.cr1.pao1.us.nlayer.net bogus rDNS: host not found [authoritative])
69.22.142.5 RTT: 82ms TTL:246 (xe-2-1-0.cr1.nyc3.us.nlayer.net bogus rDNS: host not found [authoritative])
69.31.95.145 RTT: 80ms TTL:247 (ae2-70g.cr1.ewr1.us.nlayer.net bogus rDNS: host not found [authoritative])
69.31.94.118 RTT: 80ms TTL:247 (ae1-70g.ar2.ewr1.us.nlayer.net bogus rDNS: host not found [authoritative])
69.31.95.130 RTT: 81ms TTL: 59 (as8001.xe-3-0-6.ar2.ewr1.us.nlayer.net bogus rDNS: host not found [authoritative])
209.123.10.122 RTT: 81ms TTL: 58 (0.e1-4.tbr1.oct.nac.net bogus rDNS: host not found [authoritative])
209.123.10.2 RTT: 80ms TTL:246 (vlan804.esd1.oct.nac.net bogus rDNS: host not found [authoritative])
209.123.109.175 RTT: 82ms TTL: 55 (www.dslreports.com ok)
At the third, eighth, or seventeenth hop? (No, I did not count the actual number of hops; just asking.)
Are they saving money by grouping everyone in north east via same gateway/pop? Cause the service sucks now, i can handle a few spikes in latency but their current prb with their BGP routing is getting frustrating. ANyone with 3rd party VPN tunnels built to other ISPs must have the same prbs as me.
To put is another way, do you live on a freeway off ramp?
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
 tschmidtPremium,MVM
join:2000-11-12
Milford, NH
kudos:5
·Fairpoint Commun..
 ·Hollis Hosting
| reply to JJW
said by JJW : Major latency, my packets are routed via NYC peer, outside networks intermittently cant reach my IP space.
I guess my biggest grip is why do my packets go from NH,Boston to NYC then internet. Because that is where a bunch of Internet hotels are located so Fairpoint traffic can peer with various transit carriers.
I have not saved old traceroutes but I'm pretty sure that is very similar to how NH packets were routed during Verizon's time.
/tom |
|
| reply to xQim
I had no choice to have anything but fairpoint as I live in a park and there was only fairpoint running down the poles, since time warner has strung fiber so now I have roadrunner but not 27mbps |
|
NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:4 Reviews:
·SONIC.NET
·Pacific Bell - SBC
| reply to NormanS
Too old to edit, so reply to myself. Since that last post, I have fired AT&T (no more ATTIS transit) and hired Sonic.net, LLC. Changed things, somewhat:
08/08/11 16:30:25 Slow traceroute www.dslreports.com
Trace www.dslreports.com (209.123.109.175) ...
173.228.18.1 RTT: 4ms TTL:255 (173-228-18-1.dsl.dynamic.sonic.net ok)
70.36.243.21 RTT: 5ms TTL:254 (gig1-6.cr1.lsatca11.sonic.net bogus rDNS: host not found [authoritative])
69.12.211.5 RTT: 4ms TTL:252 (0.xe-7-1-0.gw.pao1.sonic.net bogus rDNS: host not found [authoritative])
69.22.130.85 RTT: 7ms TTL:252 (xe-1-0-6.ar1.pao1.us.nlayer.net bogus rDNS: host not found [authoritative])
69.22.153.18 RTT: 5ms TTL:251 (ae0-70g.cr1.pao1.us.nlayer.net bogus rDNS: host not found [authoritative])
69.22.143.169 RTT: 7ms TTL:250 (ae1-60g.cr1.sfo1.us.nlayer.net bogus rDNS: host not found [authoritative])
69.22.142.96 RTT: 60ms TTL:246 (xe-0-0-3.cr1.slc1.us.nlayer.net bogus rDNS: host not found [authoritative])
69.22.142.101 RTT: 72ms TTL:248 (xe-5-2-0.cr1.ord1.us.nlayer.net bogus rDNS: host not found [authoritative])
69.22.142.75 RTT: 72ms TTL:246 (xe-9-2-0.cr1.ewr1.us.nlayer.net bogus rDNS: host not found [authoritative])
69.31.94.118 RTT: 78ms TTL:246 (ae1-70g.ar2.ewr1.us.nlayer.net bogus rDNS: host not found [authoritative])
69.31.95.130 RTT: 73ms TTL: 53 (as8001.xe-3-0-6.ar2.ewr1.us.nlayer.net bogus rDNS: host not found [authoritative])
209.123.10.122 RTT: 77ms TTL: 52 (0.e1-4.tbr1.oct.nac.net bogus rDNS: host not found [authoritative])
209.123.10.2 RTT: 73ms TTL:242 (vlan804.esd1.oct.nac.net bogus rDNS: host not found [authoritative])
209.123.109.175 RTT: 73ms TTL: 50 (www.dslreports.com ok)
Basically, looks like the aggregation is done closer to home (Palo Alto, California, instead of Pleasanton, California). But Sonic peers with nLayer, as did ATTIS. So most of the route is the same.
FWIW, I've seen Southern California SBC customers routed on SBCIS transit from Los Angeles, California to San José, California, where they made a peering connection with Level 3, then rode Level 3 transit back to Los Angeles, before turning east to run through DFW to Atlanta, Georgia. That amounts to a doubling back on the same path for ~800 miles (~400 miles on SBCIS transit and ~400 miles on Level 3 transit) before leaving the L.A. area for other places.
It is all a matter of where the peers want to exchange traffic. Apparently, SBC (this was before they bought AT&T, and adopted that name) got a better deal meeting Level 3 in San José, than in Los Angeles.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
|
