Announced routes
Every prefix a peer of the route collectors sees with origin AS263170, 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.
| 38.134.126.0/24 | No ROA | None | 666 99% |
| 192.141.4.0/24 | Valid | Nonecovered by 192.141.4.0/22 | 673 100% |
| 192.141.5.0/24 | Valid | Nonecovered by 192.141.4.0/22 | 673 100% |
| 192.141.6.0/24 | Valid | Nonecovered by 192.141.4.0/22 | 673 100% |
| 192.141.7.0/24 | Valid | Nonecovered by 192.141.4.0/22 | 673 100% |
| 2803:2fc0::/32 | Valid | None | 635 100% |
| 181.114.56.0/24 | Valid | RIR databaseLACNIC | 673 100% |
| 181.114.57.0/24 | Valid | RIR databaseLACNIC | 673 100% |
| 181.114.58.0/24 | Valid | RIR databaseLACNIC | 673 100% |
| 181.114.59.0/24 | Valid | RIR databaseLACNIC | 673 100% |
| 130.117.250.0/24 | Valid | RIR databaseARIN | 671 100% |
| 2803:2080::/32 | Valid | RIR databaseLACNIC | 635 100% |
AS-SET
AS263170'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 12 are in fix.csv.
- ROA: none1
- Route object: none6
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.134.126.0/24 | No ROA covers it. Add a ROA for AS263170, maxLength 24. |
| Route object: none | 38.134.126.0/24 | No route object for it. Add a route object with origin AS263170 in the RIR database for the space. |
| Route object: none | 192.141.4.0/24 | No route object for it. A route object for 192.141.4.0/22 with origin AS263170 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263170 in the RIR database for the space. |
| Route object: none | 192.141.5.0/24 | No route object for it. A route object for 192.141.4.0/22 with origin AS263170 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263170 in the RIR database for the space. |
| Route object: none | 192.141.6.0/24 | No route object for it. A route object for 192.141.4.0/22 with origin AS263170 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263170 in the RIR database for the space. |
| Route object: none | 192.141.7.0/24 | No route object for it. A route object for 192.141.4.0/22 with origin AS263170 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263170 in the RIR database for the space. |
| Route object: none | 2803:2fc0::/32 | No route object for it. Add a route object with origin AS263170 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263170 whose prefix no peer sees AS263170 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.182.20.0/22 | NTTCOM | No ROA |
| 45.226.59.0/24 | LACNIC | Valid |
| 181.114.56.0/22 | NTTCOM, RADB | No ROA |
| 192.141.4.0/22 | NTTCOM, RADB | Valid |
| 2803:910::/32 | LACNIC | Valid |
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.