[183180] in North American Network Operators' Group
RE: Cogent revisited
daemon@ATHENA.MIT.EDU (Matthew Huff)
Mon Aug 17 09:02:18 2015
X-Original-To: nanog@nanog.org
From: Matthew Huff <mhuff@ox.com>
To: "Justin M. Streiner" <streiner@cluebyfour.org>, "nanog@nanog.org"
<nanog@nanog.org>
Date: Mon, 17 Aug 2015 13:02:13 +0000
In-Reply-To: <Pine.LNX.4.64.1508162319280.734@whammy.cluebyfour.org>
Errors-To: nanog-bounces@nanog.org
There is also the problem with multi-homed customers where Cogent is in the=
mix. The dropped packets at Cogent's peering points to eyeball networks br=
eak certain protocols that are packet loss sensitive (VoIP, IPSEC, etc...).
----
Matthew Huff=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 | 1 Manhattanville Rd
Director of Operations=A0=A0=A0| Purchase, NY 10577
OTA Management LLC=A0=A0=A0=A0=A0=A0 | Phone: 914-460-4039
aim: matthewbhuff=A0=A0=A0=A0=A0=A0=A0 | Fax:=A0=A0 914-694-5669
-----Original Message-----
From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Justin M. Streine=
r
Sent: Sunday, August 16, 2015 11:27 PM
To: nanog@nanog.org
Subject: Re: Cogent revisited
On Wed, 12 Aug 2015, James Bensley wrote:
> Perhaps that depends on were are you in the world and your traffic types.
>
> I have worked with two UK ISPs that have Cogent as one of their
> transit providers, neither have had any problems in the 5+ years
> they've both had the Cogent transit, it has always "just worked".
And for the most part, that will be the case. If you're multi-homed, it's=
=20
really not a major issue. It's more when someone is:
1. single-homed to Cogent and they get into a peering/transit/pay-us spat=20
with one of the DFZ carriers, and Cogent gets de-peered. Single-homed=20
customers of $de-peering_carrier disappear from your view of the Internet.
2. single-homed to one of said DFZ carriers and a peering/transit/pay-us=20
spat arises with Cogent, and Cogent gets de-peered. Single-homed customers
of Cogent's disappear from your view of the Internet.
jms
