Article View: bc.bcnet
Article #1274Vancouver ISP net connections
From: Michael Dillon
Date: Sun, 28 Jan 1996 00:00
Date: Sun, 28 Jan 1996 00:00
95 lines
4980 bytes
4980 bytes
In article <4ec55q$6mk@morgoth.sfu.ca>,
Peter Van Epp <vanepp@news.sfu.ca> wrote:
>Thomas Dzubin <dzubint@freenet.vancouver.bc.ca> writes:
>
>
>>Does anyone have a definitive list of how the various ISPs in BC or Vancouver
>>hook into the Internet? Do any of them use BCnet for access?
>
> I don't. I don't even know who is a BCnet customer (other than the
>three Universities. I do have some non definitive information that I have
>picked up over the years which I will toss out and let more knowledgable
>people correct.
> For whichever providers are on BCnet, the CA*net links (which is
>how BCnet gets to the Internet) consist of a T3 from Vancouver to Seattle,
>and Ubiquity like Ethernet over ATM links towards Eastern Canada (I believe
>2 as with the old T1 links, but may be wrong). I have never heard a public
>answer on what the CIRs on those links are. In any case, CA*net has 2 more
>T3s to the US in Eastern Canada (one in Toronto and one in Montreal), and
>in theory (and probably in practice, the routing gods willing) a BCnet site
>can use all of these.
The Okanagan Internet Junction in Vernon B.C. has a BCnet Ubiquity
connection. We have NEVER seen congestion delays inside BCNet. Whenever I
traceroute the traffic always goes into the USA via Vancouver unless it
is to an Ontario ISP who is connected to CA*Net or accessible via the
Toronto exchange point. I have done traceroutes from a site in England on
EUNet/GB that come into CA*net at Toronto or Montreal and thence to Vernon.
> Mindlink (since you mentioned them), used to be a BCnet Ubiquity
>connected customer. Some time in the past, they changed to a Ubiquity
>connected BC Tel ACC customer. I believe that the current Ubiquity Internet
>connection is a T3 to MCI in San Fransisco, and I am somewhat suprised that
Sacramento actually.
>you report slow response. Is it possible that the limitation is between you
>and Mindlink rather than Mindlnk and the net?
Or perhaps Mindlink's internal network is poorly engineered and the
congestion starts there? Or perhaps a BCNet customer can be routed via
Toronto if there are problems inside MCI USA whereas a BC-Tel customer is
just screwed?
>may be more of the problem. BCnet was experienceing %25 to %40 packet loss
>to US destinations either this week or last week (weeks tend to blur together
>for me :-) ).
a MAJOR fibre cut in the Northeastern USA caused great havoc in traffic
patterns for several days.
> That said, as Sam pointed out in his response, Mindlink has been
>bought by Istar and like Sam I expect they will move to the Istar backbone
>(which is reputed to also be T3) when the current Ubiquity contract is up
>(but that is just speculation on my part). Some of the local providers are
>on Istar now (Wimsey is for sure, and in fact has also been bought by IStar),
Yep! Now my routing to Wimsey goes to fONOROLA in Toronto and thence to
Montreal, Ottawa and Vancouver...
>and from something Curt posted I believe that Portal is a current Istar
>customer as well.
That's right. Same traceroute as Wimsey
> In addition Cyberstore has or at least had a T1 link
>to Seattle (that is old information, and they may have upgraded),
They connect to Westel who runs a line into Seattle.
>Insinc
>had another T1 and Frame relay links around (and since their buyout by
>Sprint, things may have changed).
A traceroute to them goes through the Ontario exchange point and thence
back to Vancouver on a T1 line. They still have a T1 from Fort Worth up
into Vancouver. I did a traceroute from inside BC-Tel to check this and
was routed to Insinc via the PacBell NAP.
> There are probably a few more wholesalers
>around (presumably with customers) UUnet Canada for instance. I don't know
>who Internet Direct buys bandwidth from, they may have their own link to
>somewhere,
They have their own line (presumably a T1) direct to MCI in Seattle.
> and I think (from a traceroute) that Internet Express is a
>BCnet customer.
That's right!
--
Michael Dillon Voice: +1-604-546-8022
Memra Software Inc. Fax: +1-604-546-3049
http://www.memra.com E-mail: michael@memra.com
Technical Details
Message-ID:
<4eelhs$g2u@felix.junction.net>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<4e1lrq$764@fountain.mindlink.net> <4e1o23$fn@morgoth.sfu.ca> <4ebpi4$fkh@fountain.mindlink.net> <4ec55q$6mk@morgoth.sfu.ca>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 106393,f883634f02a18f6d X-Google-Attributes: gid106393,public X-Google-Thread: 106cdd,56f890806e9ef2c9,start X-Google-Attributes: gid106cdd,public From: michael@okjunc.junction.net (Michael Dillon) Subject: Vancouver ISP net connections Date: 1996/01/28 Message-ID: <4eelhs$g2u@felix.junction.net> X-Deja-AN: 136816571 references: <4e1lrq$764@fountain.mindlink.net> <4e1o23$fn@morgoth.sfu.ca> <4ebpi4$fkh@fountain.mindlink.net> <4ec55q$6mk@morgoth.sfu.ca> organization: Okanagan Internet Junction, Vernon B.C., Canada newsgroups: bc.bcnet,bc.general