Zayo or HE for IP transit
What is the current experience with Zayo or HE? I'm looking at possibly adding one of them into a mix of cogent and a mix from my datacenter. Would be using BGP full routes. Any experiences would be appreciated. Sincerely, James
Hurricane has probably the most peering of any large network on the planet. They also carry more v6 traffic than anyone. But they have a famous problem with v6 - you cannot get to Cogent (174) from HE. Since you have Cogent, that should not be a problem. Private, smart people, customer service is excellent, generally good network. One minor thing to keep in mind: They do not have as many weird “features” as some of the other big networks. If you are looking for something very specific (as opposed to vanilla transit), you should check to see if they support it. Not saying they won’t, just saying I would check. Which, frankly, is good advice for any network. I have not used Zayo in many years, so cannot comment on them. -- TTFN, patrick
On Apr 19, 2021, at 5:30 PM, James Lumby <james@jlent.net> wrote:
What is the current experience with Zayo or HE? I’m looking at possibly adding one of them into a mix of cogent and a mix from my datacenter. Would be using BGP full routes. Any experiences would be appreciated.
Sincerely, James
No issues with HE, only gripe was that if you had transit along with IX peering, traffic will always prefer transit over IX ports. From: NANOG <nanog-bounces+lguillory=reservetele.com@nanog.org> On Behalf Of Patrick W. Gilmore Sent: Tuesday, April 20, 2021 11:12 AM To: North American Operators' Group <nanog@nanog.org> Subject: Re: Zayo or HE for IP transit *External Email: Use Caution* Hurricane has probably the most peering of any large network on the planet. They also carry more v6 traffic than anyone. But they have a famous problem with v6 - you cannot get to Cogent (174) from HE. Since you have Cogent, that should not be a problem. Private, smart people, customer service is excellent, generally good network. One minor thing to keep in mind: They do not have as many weird “features” as some of the other big networks. If you are looking for something very specific (as opposed to vanilla transit), you should check to see if they support it. Not saying they won’t, just saying I would check. Which, frankly, is good advice for any network. I have not used Zayo in many years, so cannot comment on them. -- TTFN, patrick On Apr 19, 2021, at 5:30 PM, James Lumby <james@jlent.net<mailto:james@jlent.net>> wrote: What is the current experience with Zayo or HE? I’m looking at possibly adding one of them into a mix of cogent and a mix from my datacenter. Would be using BGP full routes. Any experiences would be appreciated. Sincerely, James
On Tue, Apr 20, 2021 at 04:28:12PM +0000, Luke Guillory wrote:
No issues with HE, only gripe was that if you had transit along with IX peering, traffic will always prefer transit over IX ports.
That's how it's supposed to work, and is not specific to HE. Customer routes > peer routes Most providers wouldn't allow simultaneous peer + customer relationship, but in this case, I would argue that HE is doing you a favor by leaving your settlement-free peering adjacency in place, for you to dump outbound traffic toward their customers for free. James
On 4/19/21 5:30 PM, James Lumby wrote:
What is the current experience with Zayo or HE? I’m looking at possibly adding one of them into a mix of cogent and a mix from my datacenter. Would be using BGP full routes. Any experiences would be appreciated.
Well AFAIK Zayo is not filtering invalid ROA's from their network. So if tht matters to you, take that into consideration. -- inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP: https://pgp.inoc.net/rblayzor/
I use both of them. I’d recommend you use either as a primary and bump cogent to secondary. Or axe cogent and use Zayo and HE. Cogent sucks. -Mike
On Apr 20, 2021, at 09:09, James Lumby <james@jlent.net> wrote:
What is the current experience with Zayo or HE? I’m looking at possibly adding one of them into a mix of cogent and a mix from my datacenter. Would be using BGP full routes. Any experiences would be appreciated.
Sincerely, James
From those two i would pick Zayo.
HE.net don't allow you to play with communities and TE. cheers /nuno On Mon, 2021-04-19 at 21:30 +0000, James Lumby wrote:
What is the current experience with Zayo or HE? I’m looking at possibly adding one of them into a mix of cogent and a mix from my datacenter. Would be using BGP full routes. Any experiences would be appreciated.
Sincerely, James
IMHO: * Zayo = worse coverage/connectivity, adequate connectivity to other Tier1/Tier2, massive fiber network * HE = less redundancy built into their network, but best-connected to leaves/edges of the internet (and still good connectivity to core) Others may have had different experiences, but that's what I see from where I sit. -Adam Adam Thompson Consultant, Infrastructure Services [1593169877849] 100 - 135 Innovation Drive Winnipeg, MB, R3T 6A8 (204) 977-6824 or 1-800-430-6404 (MB only) athompson@merlin.mb.ca<mailto:athompson@merlin.mb.ca> www.merlin.mb.ca<http://www.merlin.mb.ca/> ________________________________ From: NANOG <nanog-bounces+athompson=merlin.mb.ca@nanog.org> on behalf of James Lumby <james@jlent.net> Sent: April 19, 2021 16:30 To: nanog@nanog.org <nanog@nanog.org> Subject: Zayo or HE for IP transit What is the current experience with Zayo or HE? I’m looking at possibly adding one of them into a mix of cogent and a mix from my datacenter. Would be using BGP full routes. Any experiences would be appreciated. Sincerely, James
participants (8)
-
Adam Thompson -
James Jun -
James Lumby -
Luke Guillory -
Mike Lyon -
Nuno Vieira -
Patrick W. Gilmore -
Robert Blayzor