<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Tim,<div class=""><br class=""></div><div class="">This is really good news! Congratulations :-) </div><div class="">Will XS4all make some marketing noise about this? Twitter, press release? Something like MSK did yesterday: <a href="https://www.msk-ix.ru/en/press-center/news/?id=20190520" class="">https://www.msk-ix.ru/en/press-center/news/?id=20190520</a></div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Nathalie</div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Op 21 mei 2019, om 13:08 heeft Tim Reinders <<a href="mailto:timr@xs4all.net" class="">timr@xs4all.net</a>> het volgende geschreven:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hello all,<br class=""><br class="">AS3265 is now dropping all RPKI invalid prefixes received from (transit) peers.<br class=""><br class="">We run two geographically spread instances of Routinator.<br class="">Our peering-edge consists of two MX960 routers running "JUNOS 17.4R2-S3.2”<br class=""><br class="">As of yet no real (customer) impact, this is reflected in the volume of traffic in <br class="">netflow data containing RPKI invalid prefixes (pre/post reject)<br class=""><br class="">Remaining work is rejecting invalids on customer BGP sessions (handful) and writing<br class="">meaningful alerts for our monitoring-stack (prometheus/alertmanager)<br class=""><br class="">Regards,<br class="">Tim Reinders<br class="">XS4ALL<br class="">timr on #nlnog<br class="">_______________________________________________<br class="">NLNOG mailing list<br class=""><a href="mailto:NLNOG@nlnog.net" class="">NLNOG@nlnog.net</a><br class="">http://mailman.nlnog.net/listinfo/nlnog<br class=""></div></div></blockquote></div><br class=""></div></body></html>