Looks like they already are? https://bgp.he.net/AS14374 Depending on which peer you might be replacing 123.net or cogent with, that could possibly change someone’s opinion. However, at least from past topics on this, given cogent history with peering issues (such as HE.net cake), I think one would certainly want to understand what impact peering/routing quirks would cause them and their ability to work around them before selecting cogent. Given I doubt your international reach is a big deal, and given 123.net is more of a tier2 (https://bgp.he.net/AS12129) with local and regional peering ( https://www.peeringdb.com/net/3899 ), they could be better suited for your traffic patterns and local customers? Also if you are not already interconnected with 123.net from a transport perspective, given their footprint in the state, there could be opportunities for an NNI to expand your reach to help interconnect your customer’s locations (aka customer has a branch office inside and outside your direct footprint and wants ELAN type service). I have looked at them before but never got serious, and thus cannot offer any input on their actual service or support. From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Ben Cannon Sent: Friday, January 4, 2019 8:16 PM To: Aaron Henderson <ahenderson@avci.net> Cc: nanog@nanog.org Subject: EXT_Re: Changing upstream providers, opinions/thoughts on 123.net and cogent Run BGP and use multiple upstream providers as soon as you can. -Ben On Jan 4, 2019, at 4:57 AM, Aaron Henderson <ahenderson@avci.net<mailto:ahenderson@avci.net>> wrote: I work for a rural ISP and the powers that be have been thinking about changing our upstream providers. The big names on the table right now are 123.net<http://123.net/> and Cogent. I, along with the people in my circle, do not have any experience with these providers and all we are getting is what sales are dishing us. I was hoping some of you here might have experience with these providers and could share your experiences and opinions. Thanks, A