Yup sending an email to support (RIPE) for clarification. But Twitter NOC is adamant that they are not doing the wrong thing (advertising unallocated address space) because it shows in RADB-GRS via RIPE Whois <div class="gmail_quote"><div dir="ltr">On Thu, 12 Jul 2018 at 7:39 pm, Christoffer Hansen <<a href="mailto:netravnen@gmail.com">netravnen@gmail.com</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, 12 Jul 2018 at 13:28, Christoffer Hansen <<a href="mailto:netravnen@gmail.com" target="_blank">netravnen@gmail.com</a>> wrote: > > On Thu, 12 Jul 2018 at 12:50, Aftab Siddiqui <<a href="mailto:aftab.siddiqui@gmail.com" target="_blank">aftab.siddiqui@gmail.com</a>> wrote: > > Thanks for the detailed response and it means if the source is not RIPE then it shouldn’t be considered as authentic data because the resource belongs to RIPE NCC. > > That I am not certain about. Normally I would expect to at least find > an INETNUM object in the RIPE NCC database. If I go by the list published the RIPE NCC themself. <a href="https://ftp.ripe.net/pub/stats/ripencc/delegated-ripencc-latest" rel="noreferrer" target="_blank">https://ftp.ripe.net/pub/stats/ripencc/delegated-ripencc-latest</a> The <a href="http://188.64.224.0/21" rel="noreferrer" target="_blank">188.64.224.0/21</a> prefix is not allocated at all. Why Twitter is announcing it. < scratching head for answers > <a href="https://stat.ripe.net/188.64.224.0-188.64.231.255?sourceapp=ripedb#tabId=database" rel="noreferrer" target="_blank">https://stat.ripe.net/188.64.224.0-188.64.231.255?sourceapp=ripedb#tabId=database</a> Christoffer </blockquote></div>