Announced routes
Every prefix a peer of the route collectors sees with origin AS47143, 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.
| 91.192.118.0/24 | No ROA | Nonecovered by 91.192.116.0/22 | 673 100% |
| 91.192.119.0/24 | No ROA | Nonecovered by 91.192.116.0/22 | 673 100% |
| 195.42.103.0/24 | No ROA | Nonecovered by 195.42.102.0/23 | 673 100% |
| 207.192.114.0/24 | No ROA | Other IRR onlyRADB | 1 0%low visibility |
| 91.192.116.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 91.205.96.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.205.97.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.205.99.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 195.42.102.0/23 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS47143'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 16 are in fix.csv.
- ROA: none9
- Route object: none3
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.192.118.0/24 | No ROA covers it. Add a ROA for AS47143, maxLength 24. |
| Route object: none | 91.192.118.0/24 | No route object for it. A route object for 91.192.116.0/22 with origin AS47143 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47143 in the RIR database for the space. |
| ROA: none | 91.192.119.0/24 | No ROA covers it. Add a ROA for AS47143, maxLength 24. |
| Route object: none | 91.192.119.0/24 | No route object for it. A route object for 91.192.116.0/22 with origin AS47143 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47143 in the RIR database for the space. |
| ROA: none | 195.42.103.0/24 | No ROA covers it. Add a ROA for AS47143, maxLength 24. |
| Route object: none | 195.42.103.0/24 | No route object for it. A route object for 195.42.102.0/23 with origin AS47143 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47143 in the RIR database for the space. |
| ROA: none | 207.192.114.0/24 | No ROA covers it. Add a ROA for AS47143, maxLength 24. |
| Route object: RIR | 207.192.114.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 91.192.116.0/22 | No ROA covers it. Add a ROA for AS47143, maxLength 22. |
| ROA: none | 91.205.96.0/24 | No ROA covers it. Add a ROA for AS47143, maxLength 24. |
| ROA: none | 91.205.97.0/24 | No ROA covers it. Add a ROA for AS47143, maxLength 24. |
| ROA: none | 91.205.99.0/24 | No ROA covers it. Add a ROA for AS47143, maxLength 24. |
| ROA: none | 195.42.102.0/23 | No ROA covers it. Add a ROA for AS47143, maxLength 23. |
Route objects not announced
Route objects with origin AS47143 whose prefix no peer sees AS47143 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.205.96.0/22 | RIPE | No ROA |
| 91.205.98.0/24 | RIPE | No ROA |
| 178.214.96.0/24 | RIPE | No ROA |
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.