Kentik has been great for us on notification and analysis.
They are pretty much accurate and you can set-up tons of alerts and even action.
For example Automatic blackhole for DDoS
I wouldn’t use them to shift your traffic around (aka traffic engineering) but
I'm sure you can set that up as well.
Is your AS registered with ARIN?2 byte or 4 byte ASN number?How many devices
are you peering with?Dual homed, multi homed?Bandwidth?Type of traffic?
There are alot more...
Regards,Cyrus Ramirez
On Wednesday, July 12, 2017, 3:11:38 PM EDT, David Hofstee
wrote:
On Wed, 12 Jul 2017 11:03:50 -0700, ShaColby Jackson said:
> I know solutions like Kentik do a lot more but Iâm focusing on just the
> above use case. Also ignoring the cloud vs. on-prem difference, assume that
> doesnât matter.
Might want to re-think that. In a world where some eyeball
I know this topic has gone around a couple times but wondering if there are
any new strong opinions on inbound+outbound traffic analysis with a bonus
for excellence in traffic engineering at the edge. A typical use case would
be finding an AS or prefix representing a large volume of inbound and/or
I would state that peering gives more control over the traffic you handle
(since it is not going over someone else's network). Every hop is a
possible problem to your operations, I guess.
David
On 12 July 2017 at 09:13, Wolfgang Tremmel
wrote:
>
> > On 11. Jul
* craig washington
> Newbie question, what criteria do you look for when you decide that
> you want to peer with someone or if you will accept peering with
> someone from an ISP point of view.
Routing hygiene. I expect the would-be peer to keep the number of
advertised routes that are either 1)
> On 11. Jul 2017, at 21:43, Nick Hilliard wrote:
>
> Patrick W. Gilmore wrote:
>> 1) Are they present an IX where I am present?
>>
>> 2) Can they configure BGP correctly?
>>
>> 3) … Beer?
>
>
> 1) do they have a pulse?
4 ) are they in PeeringDB and keep their entry up to
7 matches
Mail list logo