<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Wasn't 44/8 the space for AMPRNet?</p>
    <p>I looked it up and they sold part of it to Amazon. Ok. Got it.</p>
    <p>Possible that a potential highjack could be a good faith radio
      ham who hasn't somehow been updated on the sale of that space? Or
      more likely to be a malicious highjack?<br>
    </p>
    <div class="moz-cite-prefix">On 8/23/22 02:05, Siyuan Miao wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAO3CAMqsx8+fBT11Eqs_f_01oUDSTqO4zUz78KVka_3iDiODVA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Amazon was only announcing <a
          href="http://44.224.0.0/11" moz-do-not-send="true">44.224.0.0/11</a>
        at first.
        <div><br>
        </div>
        <div><a href="https://bgp.tools/prefix/44.235.216.0/24"
            moz-do-not-send="true" class="moz-txt-link-freetext">https://bgp.tools/prefix/44.235.216.0/24</a><br>
        </div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Tue, Aug 23, 2022 at 4:03
          AM Ronald F. Guilmette <<a
            href="mailto:rfg@tristatelogic.com" moz-do-not-send="true"
            class="moz-txt-link-freetext">rfg@tristatelogic.com</a>>
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">In
          message <<a
href="mailto:CAO3CAMoT9gC_Evd-CcZg06A-o_MajmLtxLHbXFnauDoMyqoSYg@mail.gmail.com"
            target="_blank" moz-do-not-send="true"
            class="moz-txt-link-freetext">CAO3CAMoT9gC_Evd-CcZg06A-o_MajmLtxLHbXFnauDoMyqoSYg@mail.gmail.com</a>>,
          <br>
          Siyuan Miao <<a href="mailto:siyuan@misaka.io"
            target="_blank" moz-do-not-send="true"
            class="moz-txt-link-freetext">siyuan@misaka.io</a>>
          wrote:<br>
          <br>
          >Hjacking didn't last too long. AWS started announcing a
          more specific<br>
          >announcement to prevent hijacking around 3 hours later.
          Kudos to Amazon's<br>
          >security team :-)<br>
          <br>
          Sorry.  I'm missing something here.  If the hijack was of <a
            href="http://44.235.216.0/24" rel="noreferrer"
            target="_blank" moz-do-not-send="true">44.235.216.0/24</a>,
          then<br>
          how did AWS propagate a "more specific" than that?<br>
          <br>
          <br>
          Regards,<br>
          rfg<br>
          <br>
          -- <br>
          <br>
          To unsubscribe from this mailing list, get a password
          reminder, or change your subscription options, please visit: <a
            href="https://lists.ripe.net/mailman/listinfo/anti-abuse-wg"
            rel="noreferrer" target="_blank" moz-do-not-send="true"
            class="moz-txt-link-freetext">https://lists.ripe.net/mailman/listinfo/anti-abuse-wg</a><br>
        </blockquote>
      </div>
    </blockquote>
  </body>
</html>