Performance metrics used in commercial BGP route optimizers

Tue Jul 16 17:24:39 UTC 2019

So I got this from BGPmon, earlier today:

*****

You received this email because you are subscribed to BGPmon.net.
For more details about these updates please visit:
https://portal.bgpmon.net/myalerts.php

====================================================================
RPKI Validation Failed (Code: 9)
====================================================================
Your prefix:          105.16.0.0/12:
Prefix Description:   In case of abuse, please contact abuse at seacom.mu
Update time:          2019-07-16 15:45 (UTC)
Detected by #peers:   1
Detected prefix:      105.26.205.62/32
Announced by:         AS65075 (-Private Use AS-)
Upstream AS:          AS53089 (IDC TELECOM LTDA EPP, BR)
ASpath:               53089 65075
Alert details:       
https://portal.bgpmon.net/alerts.php?details&alert_id=89182454
Mark as false alert:  https://portal.bgpmon.net/fp.php?aid=89182454
RPKI Status:          ROA validation failed: Invalid Prefix-Length +
Invalid Origin ASN, expected 37100

--------------------------------------------------------------
 *for questions regarding the change code or other question, please see:
https://portal.bgpmon.net/faq.php

Latest BGPmon news: http://bgpmon.net/blog/
  * Popular Destinations rerouted to Russia
  * Todayâ€™s BGP leak in Brazil
  * BGP leak causing Internet outages in Japan and beyond.

.

*****

See why we like (not!) BGP optimizers so much?

Mark.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190716/214f79d1/attachment.html>