Announced routes
Every prefix a peer of the route collectors sees with origin AS36941, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 196.223.178.0/24 | No ROA | Nonecovered by 196.223.176.0/20 | 671 100% |
| 41.216.224.0/22 | No ROA | RIR databaseAFRINIC, RIPE-NONAUTH | 673 100% |
| 196.2.80.0/20 | No ROA | RIR databaseAFRINIC | 673 100% |
| 196.223.176.0/20 | No ROA | RIR databaseAFRINIC | 673 100% |
| 2c0f:f378::/32 | No ROA | RIR databaseAFRINIC | 635 100% |
AS-SET
AS36941's PeeringDB record names no AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 6 are in fix.csv.
- ROA: none5
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 196.223.178.0/24 | No ROA covers it. Add a ROA for AS36941, maxLength 24. |
| Route object: none | 196.223.178.0/24 | No route object for it. A route object for 196.223.176.0/20 with origin AS36941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36941 in the RIR database for the space. |
| ROA: none | 41.216.224.0/22 | No ROA covers it. Add a ROA for AS36941, maxLength 22. |
| ROA: none | 196.2.80.0/20 | No ROA covers it. Add a ROA for AS36941, maxLength 20. |
| ROA: none | 196.223.176.0/20 | No ROA covers it. Add a ROA for AS36941, maxLength 20. |
| ROA: none | 2c0f:f378::/32 | No ROA covers it. Add a ROA for AS36941, maxLength 32. |
Route objects not announced
Every route object with origin AS36941 is announced.
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.