nanog mailing list archives
RE: Cogent revisited
From: Matthew Huff <mhuff () ox com>
Date: Mon, 17 Aug 2015 13:02:13 +0000
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 break certain protocols that are packet loss sensitive (VoIP, IPSEC, etc...). ---- Matthew Huff | 1 Manhattanville Rd Director of Operations | Purchase, NY 10577 OTA Management LLC | Phone: 914-460-4039 aim: matthewbhuff | Fax: 914-694-5669 -----Original Message----- From: NANOG [mailto:nanog-bounces () nanog org] On Behalf Of Justin M. Streiner 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 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 with one of the DFZ carriers, and Cogent gets de-peered. Single-homed 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 spat arises with Cogent, and Cogent gets de-peered. Single-homed customers of Cogent's disappear from your view of the Internet. jms
Current thread:
- Cogent revisited Adam Greene (Aug 11)
- Message not available
- RE: Cogent revisited Adam Greene (Aug 11)
- Re: Cogent revisited James Bensley (Aug 12)
- Re: Cogent revisited Justin M. Streiner (Aug 16)
- RE: Cogent revisited Matthew Huff (Aug 17)
- RE: Cogent revisited Adam Greene (Aug 11)
- Message not available