Announced routes
Every prefix a peer of the route collectors sees with origin AS19281, 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.
| 2001:690:200c::/48 | Invalid: origin | None | 5 1%low visibility |
| 2c0f:6300:2:100::/56 | Invalid: origin | None | 1 0%low visibility |
| 2c0f:6300:2:200::/56 | Invalid: origin | None | 1 0%low visibility |
| 199.249.255.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 9.9.9.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 149.112.112.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 149.112.149.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 147.72.242.0/24 | Valid | RIR databaseARIN | 668 99% |
| 2620:fe::/48 | Valid | RIR databaseARIN, RADB | 636 100% |
AS-SET
AS19281'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 10 are in fix.csv.
- ROA: origin3
- Route object: none3
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2001:690:200c::/48 | ROAs covering it name AS1930, not AS19281. If AS19281 should announce it, add a ROA for AS19281. |
| Route object: none | 2001:690:200c::/48 | No route object for it. Add a route object with origin AS19281 in the RIR database for the space. |
| ROA: origin | 2c0f:6300:2:100::/56 | ROAs covering it name AS328977, not AS19281. If AS19281 should announce it, add a ROA for AS19281. |
| Route object: none | 2c0f:6300:2:100::/56 | No route object for it. Add a route object with origin AS19281 in the RIR database for the space. |
| ROA: origin | 2c0f:6300:2:200::/56 | ROAs covering it name AS328977, not AS19281. If AS19281 should announce it, add a ROA for AS19281. |
| Route object: none | 2c0f:6300:2:200::/56 | No route object for it. Add a route object with origin AS19281 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS19281 whose prefix no peer sees AS19281 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2602:807:e000::/40 | ARIN | Valid |
| 2602:807:e0fe::/47 | ARIN, RADB | Valid |
| 2602:807:e0fe::/48 | ARIN, RADB | Valid |
| 2602:807:e0ff::/48 | ARIN, RADB | 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.