This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/anti-abuse-wg@ripe.net/
[anti-abuse-wg] Yet another BGP hijacking towards AS16509
- Previous message (by thread): [anti-abuse-wg] Yet another BGP hijacking towards AS16509
- Next message (by thread): [anti-abuse-wg] Yet another BGP hijacking towards AS16509
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Tue Aug 23 04:03:19 CEST 2022
In message <CAO3CAMoT9gC_Evd-CcZg06A-o_MajmLtxLHbXFnauDoMyqoSYg at mail.gmail.com>, Siyuan Miao <siyuan at misaka.io> wrote: >Hjacking didn't last too long. AWS started announcing a more specific >announcement to prevent hijacking around 3 hours later. Kudos to Amazon's >security team :-) Sorry. I'm missing something here. If the hijack was of 44.235.216.0/24, then how did AWS propagate a "more specific" than that? Regards, rfg
- Previous message (by thread): [anti-abuse-wg] Yet another BGP hijacking towards AS16509
- Next message (by thread): [anti-abuse-wg] Yet another BGP hijacking towards AS16509
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]