AS397031 here, located in Telehouse (7 Teleport). We picked up a port on
NYIIX specifically to peer with google and cloudflare. We were doing
around 6gbps inbound from google over the NYIIX for some time then
without warning google withdrew routes from us, I'm guessing because too
much bandwidt
Have no history/background that I can share.
In terms of actions, this seems obvious, but…
Look at the AS Paths fo the hijacked prefixes announced from 57129 and start
with the
second to last AS and work backwards asking that at least those prefixes from
57129 be
rejected/filtered.
Most legiti
Peace,
On Mon, Aug 26, 2019, 9:54 PM Jared Mauch wrote:
> We do our own internal monitoring of our announcements for now.
Good for you and your customers! That is already a clear signal of an
extraordinary service to your customers.
Not to underestimate your effort which I respect, but the o
Sean,
> On Aug 26, 2019, at 2:43 PM, Töma Gavrichenkov wrote:
>
> Peace,
>
> On Mon, Aug 26, 2019, 8:05 PM Sean Donelan wrote:
> Do any major ISPs have SLA language about monitoring inter-provider
> agreements for route hijacking, route leaks, address spoofing, and so on?
>
> I'm looking for
Peace,
On Mon, Aug 26, 2019, 8:05 PM Sean Donelan wrote:
> Do any major ISPs have SLA language about monitoring inter-provider
> agreements for route hijacking, route leaks, address spoofing, and so on?
>
> I'm looking for something more proactive than waiting for a customer to
> notice a proble
Do any major ISPs have SLA language about monitoring inter-provider
agreements for route hijacking, route leaks, address spoofing, and so on?
I'm looking for something more proactive than waiting for a customer to
notice a problem and open a trouble ticket.
6 matches
Mail list logo
