Zayo vs Coent
nickdwhite at gmail.com
Mon Nov 12 22:19:55 UTC 2018
I actually went through this exercise recently with Cogent, Zayo, and two
other providers. The requests were all made via email at roughly the same
time. HE was by far the quickest (I think under an hour), with Cogent being
about half a day initially (but they did miss a BGP session, which was
fixed within a few hours of notifying them), and Zayo taking about 3 days,
with a follow up call around the 2 day mark.
>From an outage standpoint: I've had three outages with Zayo, the first
being the most painful (left hand doesn't talk to right hand), the second
was brief and they provided an RFO same-day, and the third being similar to
the first, but resolved quicker because I was able to reference details
from the first. I've never had total outages with Cogent on my transit, but
I have on transport, and they were relatively quick to respond, resolve, or
provide details from third-party providers each time. From a quality
standpoint, I "feel" like the Zayo transit is better, but maybe that's
because I pay more for it. I think from a peering standpoint, I tend to see
better paths through Zayo. I've seen Cogent send traffic way out of region
for several content providers - causing customers to complain about high
latency to Google.
On Mon, Nov 12, 2018 at 3:09 PM John Von Essen <john at quonix.net> wrote:
> Zayo is probably a tad better in the network quality, but… Zayo’s NCC is
> awful when it comes to fixing or resolving anything, even something as
> simply as add a default route to my BGP session. And its takes forever,
> like a whole day waiting in queue. Cogent, you can call, and 15 minutes
> your done.
> > On Nov 9, 2018, at 1:18 PM, Dovid Bender <dovid at telecurve.com> wrote:
> > Hi,
> > We are in a facility where my only options are Cogent or Zayo. We plan
> on getting a 10G connection for a web crawler using v4 only. Looking for
> feedback on either or (keeping the politics out of it).
> > TIA.
> > Dovid
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NANOG