[anti-abuse-wg] Yet another BGP hijacking towards AS16509
- Previous message (by thread): [anti-abuse-wg] Yet another BGP hijacking towards AS16509
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Siyuan Miao
siyuan at misaka.io
Tue Aug 23 04:05:16 CEST 2022
Amazon was only announcing 44.224.0.0/11 at first. https://bgp.tools/prefix/44.235.216.0/24 On Tue, Aug 23, 2022 at 4:03 AM Ronald F. Guilmette <rfg at tristatelogic.com> wrote: > 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 > > -- > > To unsubscribe from this mailing list, get a password reminder, or change > your subscription options, please visit: > https://lists.ripe.net/mailman/listinfo/anti-abuse-wg > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/anti-abuse-wg/attachments/20220823/c1cfcfcf/attachment.html>
- Previous message (by thread): [anti-abuse-wg] Yet another BGP hijacking towards AS16509
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]