Announced routes
Every prefix a peer of the route collectors sees with origin AS19181, 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.
| 163.5.204.0/24 | Invalid: origin | Other origin only | 9 1%low visibility |
| 131.153.56.0/24 | Valid | None | 671 100% |
| 131.153.57.0/24 | Valid | None | 671 100% |
| 131.153.58.0/23 | Valid | None | 671 100% |
| 131.153.83.0/24 | Valid | None | 671 100% |
| 131.153.164.0/24 | Valid | None | 671 100% |
| 131.153.166.0/23 | Valid | None | 671 100% |
| 131.153.224.0/24 | Valid | None | 671 100% |
| 131.153.233.0/24 | Valid | None | 670 100% |
| 2607:6003:2307::/48 | Valid | None | 633 100% |
| 2607:ff00:700::/40 | Valid | None | 633 100% |
| 2607:ff00:70b::/48 | Valid | None | 633 100% |
| 2607:ff00:70d::/48 | Valid | None | 633 100% |
AS-SET
AS19181'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 15 are in fix.csv.
- ROA: origin1
- Route object: none13
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 163.5.204.0/24 | ROAs covering it name AS198566, not AS19181. If AS19181 should announce it, add a ROA for AS19181. |
| Route object: none | 163.5.204.0/24 | Route objects for it name AS198566. Add a route object with origin AS19181 in the RIR database for the space. |
| Route object: none | 131.153.56.0/24 | No route object for it. Add a route object with origin AS19181 in the RIR database for the space. |
| Route object: none | 131.153.57.0/24 | No route object for it. Add a route object with origin AS19181 in the RIR database for the space. |
| Route object: none | 131.153.58.0/23 | No route object for it. Add a route object with origin AS19181 in the RIR database for the space. |
| Route object: none | 131.153.83.0/24 | No route object for it. Add a route object with origin AS19181 in the RIR database for the space. |
| Route object: none | 131.153.164.0/24 | No route object for it. Add a route object with origin AS19181 in the RIR database for the space. |
| Route object: none | 131.153.166.0/23 | No route object for it. Add a route object with origin AS19181 in the RIR database for the space. |
| Route object: none | 131.153.224.0/24 | No route object for it. Add a route object with origin AS19181 in the RIR database for the space. |
| Route object: none | 131.153.233.0/24 | No route object for it. Add a route object with origin AS19181 in the RIR database for the space. |
| Route object: none | 2607:6003:2307::/48 | No route object for it. Add a route object with origin AS19181 in the RIR database for the space. |
| Route object: none | 2607:ff00:700::/40 | No route object for it. Add a route object with origin AS19181 in the RIR database for the space. |
| Route object: none | 2607:ff00:70b::/48 | No route object for it. Add a route object with origin AS19181 in the RIR database for the space. |
| Route object: none | 2607:ff00:70d::/48 | No route object for it. Add a route object with origin AS19181 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS19181 whose prefix no peer sees AS19181 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 206.214.64.0/19 | RADB | 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.