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
wrote:
> In message <
> cao3camot9gc_evd-cczg06a-o_majmltxlhbxfnaudomyqo...@mail.gmail.com>,
> Siyuan Miao wrote:
>
> >Hjacking didn't last too long.
In message
,
Siyuan Miao 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 propa
Just noticed another thing:
➜ ~ whois -h whois.ripe.net -- "--list-versions AS1299" | tail -n10
2862 2022-07-11T14:44:49Z ADD/UPD
2863 2022-07-27T11:17:25Z ADD/UPD
2864 2022-08-02T08:43:02Z ADD/UPD
2865 2022-08-10T12:11:29Z ADD/UPD
*2866 2022-08-17T10:47:43Z ADD/UPD2867 2022-08-18T12
Hi folks,
Recently I read a post regarding the recent incident of Celer Network and
noticed a very interesting and successful BGP hijacking towards AS16509.
The attacker AS209243 added AS16509 to their AS-SET and a more specific
route object for the /24 where the victim's website is in ALTDB:
(Be
