Who is the ISP for Bell Atlantic?
Ray Bonar
Here in New York City, Bell Atlantic is currently rolling out their
DSL. Bell Atlantic.net is their provider, but ba.net uses what they
call a GSP (global service provider). Bell Atlantic is in fact
reselling another ISP's services.
I can't find anyone at Bell Atlantic who knows who that GSP for DSL
is. I've been told that it could possibly be Quest or GTE. Most
people manning the info phones for Bell Atlantic DSL just don't know
(but at least they admit it).
Some idea about the completeness of usenet postings (in mp3 and
similar groups) would seem to be a central issue before committing to
a years worth of service. Can anyone comment on their experiences
with the Bell Atlantic.net service through DSL? Maybe even reveal who
that GPS is in New York?
Ray Bonar
Jimmy Chen
news:37a50bfd...@news.mindspring.com...
> I can't find anyone at Bell Atlantic who knows who that GSP for DSL
> is. I've been told that it could possibly be Quest or GTE.
For NYC, BA uses IBMNet for their ISP service. However, IBM has recently sold
their internet network to ATT. From what I remember of the sale terms, the
network it is still under the IBM name, but run by ATT.
jc
DavidB
place yet. This is from the IBM support people in their news group. Also, I
am not sure that Infospeed users in NYC are connected to IBMNET like I am
with my BA dial-up service. David
Jimmy Chen <jimmy...@mindspring.com> wrote in message
news:7ntgd2$ne5$1...@nntp4.atl.mindspring.net...
Ken Fowler
> Some idea about the completeness of usenet postings (in mp3 and
> similar groups) would seem to be a central issue before committing to
> a years worth of service. Can anyone comment on their experiences
> with the Bell Atlantic.net service through DSL? Maybe even reveal who
> that GPS is in New York?
BellAtlantic.net uses the Iconnet backbone for their ADSL service in
DC, MA, NJ, NY, and PA. Icon CMT, or Iconnet, as you probably know,
was recently acquired by Qwest Communications; Qwest has recently begun
the integration of Iconnet into their infrastructure, although that job
is far from complete.
Two months ago, BellAtlantic.net began exhibiting bandwidth issues
during peak business hours (i.e. 11am - 2pm; occasionally til 4pm) in
several regions. This "slowdown" did not substantially affect those on
the 640kbit plan, but was very noticable to many on 1.6 and 7.1mbit
plans. Not long thereafter, throughput problems mostly subsided,
apparently the result of a DS3 to OC3 connection point upgrade,
although that I have been unable to positively confirm.
Icon CMT, or Iconnet, certainly isn't considered among the best
Internet connection points, although I have yet to find another
provider with a more capable connection, let alone one with an OC3 to
the Bell Atlantic Infospeed routing point. CAIS is certainly an
option, although I hear they require a separate web login and impose
restrictions on incoming connections (UDP packets, etc). Most of the
other third-party providers listed on Bell Atlantic's site have DS3's
or less to Above.net, Cais.net, Genuity.net, or Verio.net. No others,
as best I can tell, have their own connections at ma-east.
A few sample tracerts as of 12:05PM EST:
Tracing route to wcarchive.cdrom.com [209.155.82.18]
over a maximum of 30 hops:
1 29 ms 34 ms 29 ms adsl-151-200-15-1.bellatlantic.net
2 33 ms 32 ms 34 ms 151.200.4.66
3 36 ms 33 ms 33 ms 205.171.59.29
4 27 ms 32 ms 27 ms wdc-core-01.inet.qwest.net
5 31 ms 34 ms 30 ms wdc-brdr-01.inet.qwest.net
6 38 ms 35 ms 36 ms 205.171.4.162
7 122 ms 127 ms 126 ms vva1-sfo2.ATM.us.crl.net [165.113.0.253]
8 123 ms 119 ms 127 ms wcarchive.cdrom.com [209.155.82.18]
Tracing route to www.cais.com [209.8.1.120]
over a maximum of 30 hops:
1 32 ms 37 ms 31 ms adsl-151-200-15-1.bellatlantic.net
2 33 ms 31 ms 34 ms 151.200.4.66
3 36 ms 32 ms 31 ms 151.200.0.3
4 39 ms 41 ms 41 ms Hssi10-0.core1.dca1.IConNet.NET
5 41 ms 41 ms 42 ms POS0-0-0.peer1.dca1.IConNet.NET
6 35 ms 42 ms 41 ms mae-east1.cais.net [192.41.177.96]
7 45 ms 45 ms 41 ms fe1-0.me1.cais.net [209.8.159.30]
8 41 ms 43 ms 43 ms hssi12-0.mcl1.cais.net [209.8.159.26]
9 48 ms 42 ms 47 ms fe3-1.mcl2.cais.net [209.8.159.42]
10 41 ms 36 ms 43 ms www.cais.com [209.8.1.120]
Tracing route to www.bellatlantic.net [199.45.39.41]
over a maximum of 30 hops:
1 29 ms 33 ms 36 ms adsl-151-200-15-1.bellatlantic.net
2 38 ms 37 ms 31 ms 151.200.4.66
3 36 ms 32 ms 39 ms www.bellatlantic.net [199.45.39.41]
Please note that latency with Bell Atlantic Infospeed does not appear
to vary much by distance from the central office (i.e. 1000ft vs
4000ft). Latency does, however, appear to vary with each Infospeed
plan (640kbit, 1.6mbit, 7.1mbit). As an example, my latency dropped
from a typical 45-55ms to 25-35ms (depending on time of day) when I
moved from the 640kbit plan to the 1.6mbit plan. Likewise, I have a
neighbor that moved from the 640kbit plan to the 7.1mbit plan and found
a similar drop in latency-- 45-55ms to 20-30ms.
Latency also appears to vary substantially depending on the central
office. I have talked with customers on other COs who've had some
interesting results to report. Most find latency on their 640kbit
plans to range from 35ms to 60ms, although there do appear to be
exceptions-- like 151.200.20.xxx (200 = DC/VA, 20 = CO#, xxx = customer
#) customers-- who tend to find pings of 5ms to <15ms to most sites in
the northeast. I cannot explain these differences in latency.
Hope this helps,
Ken
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
Miguel Cruz
> Latency also appears to vary substantially depending on the central
> office. I have talked with customers on other COs who've had some
> interesting results to report. Most find latency on their 640kbit
> plans to range from 35ms to 60ms, although there do appear to be
> exceptions-- like 151.200.20.xxx (200 = DC/VA, 20 = CO#, xxx = customer
> #) customers-- who tend to find pings of 5ms to <15ms to most sites in
> the northeast. I cannot explain these differences in latency.
FWIW, 25-30ms in .200.19. Perhaps the more densely-populated areas have
higher-capacity equipment in anticipation of future needs.
miguel
David Cary Hart
all inquiries, support, etc., NYC customers are considered NJ csutomers. I
had BA.net once and it offered far more LAL's than Bellatlantic.net.
Ray Bonar <bo...@tiac.net> wrote in message
news:37a50bfd...@news.mindspring.com...
> Hi;
>
> Here in New York City, Bell Atlantic is currently rolling out their
> DSL. Bell Atlantic.net is their provider, but ba.net uses what they
> call a GSP (global service provider). Bell Atlantic is in fact
> reselling another ISP's services.
>
> I can't find anyone at Bell Atlantic who knows who that GSP for DSL
> is. I've been told that it could possibly be Quest or GTE. Most
> people manning the info phones for Bell Atlantic DSL just don't know
> (but at least they admit it).
>
> Some idea about the completeness of usenet postings (in mp3 and
> similar groups) would seem to be a central issue before committing to
> a years worth of service. Can anyone comment on their experiences
> with the Bell Atlantic.net service through DSL? Maybe even reveal who
> that GPS is in New York?
>
> Ray Bonar
DavidB
IBM. For DSL, BA is using in NYC Internet Channels according to their web
pages www.banet.com and www.bellatlantic.com www.ba.net is NOT Bell
Atlantic. David
David Cary Hart <davi...@caryhart.com> wrote in message
news:kc_o3.323$wC.4...@typhoon1.gnilink.net...
Ken Fowler
"DavidB" <davidby*NOS...@banet.net> wrote:
> Belatlantic.net and Banet.net are the same thing and the ISP
> service IS from IBM. For DSL, BA is using in NYC Internet Channels
> according to their web
This is not accurate. The providers listed on http://www.bell-
atl.com/adsl/more_info/pricing_isps.html, like Internet Channel, have
nothing to do with Bellatlantic.net; they are alternatives to
Bellatlantic.net.
[repost]
Once again, BellAtlantic.net uses the Iconnet backbone for their ADSL
service in DC, MA, NJ, NY, PA, and VA. Icon CMT, or Iconnet, was
recently acquired by Qwest Communications; Qwest has recently begun the
integration of Iconnet into their infrastructure, although that job is
far from complete.
A few sample tracerts as of 12:05PM EST:
Tracing route to wcarchive.cdrom.com [209.155.82.18]
over a maximum of 30 hops:
1 29 ms 34 ms 29 ms adsl-151-200-15-1.bellatlantic.net
2 33 ms 32 ms 34 ms 151.200.4.66
3 36 ms 33 ms 33 ms 205.171.59.29
4 27 ms 32 ms 27 ms wdc-core-01.inet.qwest.net
5 31 ms 34 ms 30 ms wdc-brdr-01.inet.qwest.net
6 38 ms 35 ms 36 ms 205.171.4.162
7 122 ms 127 ms 126 ms vva1-sfo2.ATM.us.crl.net [165.113.0.253]
8 123 ms 119 ms 127 ms wcarchive.cdrom.com [209.155.82.18]
Tracing route to www.cais.com [209.8.1.120]
over a maximum of 30 hops:
1 32 ms 37 ms 31 ms adsl-151-200-15-1.bellatlantic.net
2 33 ms 31 ms 34 ms 151.200.4.66
3 36 ms 32 ms 31 ms 151.200.0.3
4 39 ms 41 ms 41 ms Hssi10-0.core1.dca1.IConNet.NET
5 41 ms 41 ms 42 ms POS0-0-0.peer1.dca1.IConNet.NET
6 35 ms 42 ms 41 ms mae-east1.cais.net [192.41.177.96]
7 45 ms 45 ms 41 ms fe1-0.me1.cais.net [209.8.159.30]
8 41 ms 43 ms 43 ms hssi12-0.mcl1.cais.net [209.8.159.26]
9 48 ms 42 ms 47 ms fe3-1.mcl2.cais.net [209.8.159.42]
10 41 ms 36 ms 43 ms www.cais.com [209.8.1.120]
Cheers!
Ruth Estep
DavidB <davidby*NOS...@banet.net> wrote in message
news:37a2...@news3.us.ibm.net...
> To the best of my knowledge, the transfer is imminent but has not taken
> place yet. This is from the IBM support people in their news group. Also,
I
> am not sure that Infospeed users in NYC are connected to IBMNET like I am
> with my BA dial-up service. David
AT&T Worldnet is buying IBMNET in its entirety; however, because of IBMNET's
sheer size, the deal also falls under FCC and Justice Department scrutiny.
Christopher L. Estep