[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Cogent & HE
- Subject: Cogent & HE
- From: jay.hanke at mankatonetworks.com (Jay Hanke)
- Date: Wed, 8 Jun 2011 15:47:09 -0500
- In-reply-to: <003501cc2619$7a1a8ce0$6e4fa6a0$@org>
- References: <1139995622-1307562524-cardhu_decombobulator_blackberry.rim.net-510085940-@b11.c14.bise6.blackberry> <[email protected]> <[email protected]> <003501cc2619$7a1a8ce0$6e4fa6a0$@org>
On Wed, Jun 8, 2011 at 3:19 PM, Paul Stewart <paul at paulstewart.org> wrote:
> Or peer with HE and buy transit from Cogent (or someone on Cogent's friendly
> list) - this is where I think their strategy is going to go after a while
> with a lot of folks (if they have the option - that's the key). ?HE will
> peer with anyone I believe - Cogent has much more stringent "tier1" rules on
> peering.
How divided is the table? I see about 98 routes transiting Cogent ASN
via a HE connection. Customer has only has HE as v6 upstream. An
previous post listed about a 1300 prefix difference. That's pretty
significant unless it's due to aggregation or something. I'd also be
interested to see the size of the other major carriers v6 tables so I
can patch a whole until the other upstream is ready.
Jay
- Follow-Ups:
- Cogent & HE
- From: paul at paulstewart.org (Paul Stewart)