I think what caused initial confusion and my identification of the wrong "Fusion Network" was that AS11696 doesn't appear to have a peeringdb page. In my recent experience with internal documentation for 40+ peers that are equal to or larger than them in size, it's the first AS I've seen without one...
https://bgp.he.net/AS11696 On the west coast it appears the Primus AS is still its own separate thing, based on a recent fix to peering and looking at route-views. On Tue, Jun 18, 2019 at 2:34 PM Erik Sundberg <esundb...@nitelusa.com> wrote: > The Globalinx network was migrated into the Fusion network earlier this > year about 27 Weeks Ago is what my router interface tells me. We ended up > running new interconnects with them and changing peering from Globalinx’s > ASN to the Fusion Network ASN 11696. The birch ASN 17184 is reachable via > AS11696. I am not sure if this was a special setup for us or not. > > > > This is for the legacy Globalinx Network AS46191 199.x.84.0/24 and > 199.x.85.0/24 if you were connecting to the 5Linx / Globalinx Broadsoft > environment. > > > > > > -Erik > > > > > > > > *From:* NANOG <nanog-boun...@nanog.org> *On Behalf Of *Mike Hammett > *Sent:* Tuesday, June 18, 2019 2:18 PM > *To:* Eric Kuhnke <eric.kuh...@gmail.com> > *Cc:* nanog@nanog.org list <nanog@nanog.org> > *Subject:* Re: Birch/Primus/Fusion Network ASN integration? > > > > I connect to Globalinx (another Birch acquisition) via AS17184. It looks > like they also have AS16526. > > > > ----- > Mike Hammett > Intelligent Computing Solutions <http://www.ics-il.com/> > <https://www.facebook.com/ICSIL> > <https://plus.google.com/+IntelligentComputingSolutionsDeKalb> > <https://www.linkedin.com/company/intelligent-computing-solutions> > <https://twitter.com/ICSIL> > Midwest Internet Exchange <http://www.midwest-ix.com/> > <https://www.facebook.com/mdwestix> > <https://www.linkedin.com/company/midwest-internet-exchange> > <https://twitter.com/mdwestix> > The Brothers WISP <http://www.thebrotherswisp.com/> > <https://www.facebook.com/thebrotherswisp> > <https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg> > ------------------------------ > > *From: *"Eric Kuhnke" <eric.kuh...@gmail.com> > *To: *"TJ Trout" <t...@pcguys.us> > *Cc: *"nanog@nanog.org list" <nanog@nanog.org> > *Sent: *Tuesday, June 18, 2019 3:13:11 AM > *Subject: *Re: Birch/Primus/Fusion Network ASN integration? > > Mea culpa. I'm actually not finding much for Fusion Connect Inc. in terms > of normal BGP presence (peeringdb page, an AS that's known to tools like > the bgp.he.net tool, etc. > > > > https://en.wikipedia.org/wiki/Birch_Communications > > > > AS20175 Birch Communications Inc. doesn't appear to be doing much of > anything > > > > There's also this, which is one of their earlier acquisitions: > https://www.peeringdb.com/net/3238 > > > > > > On Tue, Jun 18, 2019 at 12:42 AM TJ Trout <t...@pcguys.us> wrote: > > wrong fusion on peering db > > > > On Mon, Jun 17, 2019 at 10:35 PM Eric Kuhnke <eric.kuh...@gmail.com> > wrote: > > Hey all, > > > > I'm looking for any info that might be publicly available regarding > intentions to merge the Primus ASN into Birch/Fusion Network, or whether it > will remain its own thing. > > > > Primus acquired by Birch: > https://primus.ca/index.php/bc_en/news-and-events/primus-news-birch-completes-purchase-of-primus-telecommunications-assets-in-canada/ > > > > Birch acquired by Fusion: > https://primus.ca/index.php/yt_en/news-and-events/primus-news-fusion-announces-closing-of-birch-acquisition/ > > > > primus: https://www.peeringdb.com/net/2811 > > > > fusion: https://www.peeringdb.com/net/4608 > > > > ------------------------------ > > CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files > or previous e-mail messages attached to it may contain confidential > information that is legally privileged. If you are not the intended > recipient, or a person responsible for delivering it to the intended > recipient, you are hereby notified that any disclosure, copying, > distribution or use of any of the information contained in or attached to > this transmission is STRICTLY PROHIBITED. If you have received this > transmission in error please notify the sender immediately by replying to > this e-mail. You must destroy the original transmission and its attachments > without reading or saving in any manner. Thank you. >