Filtering: M1-M4 (Action 1)
The Filtering score averages metrics M1 through M4: routing incidents attributed to your ASN, and to your customer cone (the C variants), during the month:
- M2 / M2C (misoriginations / hijacks), detected by GRIP (Georgia Tech's Routing Information Project). Route-leak detection (M1 / M1C) is not yet sourced.
- M3 / M3C (bogon prefixes) and M4 / M4C (bogon ASNs), announcements of unallocated or reserved space observed in global BGP.
Incident weighting
Penalty scales with incident duration:
| Duration | Penalty |
|---|---|
| Under 30 minutes | 0.5 × weight |
| 30 minutes to 24 hours | 1 × weight |
| Over 24 hours | grows per additional day |
Incidents caused by your customers (the M1C-M4C variants) also affect your score, at reduced weight. MANRS expects you to filter customer announcements.
Score scale
No incidents means 100%. Accumulated raw penalty of 1.5 is about 80% (the OK threshold); 5.0 is about 60%.
Disputing an incident
The quickest way to flag a wrong incident is the incident feedback option on your ASN detail page: mark it as a legitimate update, note that some of the data is incorrect, or that the announcement came from a lateral peer rather than a customer. Feedback submitted during the monthly feedback window is reviewed and folded into the recalculated score.
Incidents come from GRIP's public feed, and each one in your conformance report links to its GRIP event ID. You can also report a misclassification to GRIP directly at grip-info@cc.gatech.edu. For anything the feedback options don't cover, open a support ticket with the event ID and an explanation.
If you announce bogon or Class E space as part of a documented research project, tell us. Intentional non-conformance can be noted on your record.