Announced routes
Every prefix a peer of the route collectors sees with origin AS218668, 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.
| 44.30.180.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 2602:f92a:1312::/48 | Valid | RIR databaseARIN, RADB | 635 100% |
| 2602:f92a:1322::/48 | Valid | RIR databaseARIN, RADB | 635 100% |
| 2602:f92a:1320::/48 | Valid | RIR databaseARIN, RADB | 634 100% |
| 2602:f92a:1323::/48 | Valid | RIR databaseARIN, RADB | 634 100% |
| 2602:f92a:1324::/48 | Valid | RIR databaseARIN, RADB | 633 100% |
| 2602:f2dc:9d::/48 | Valid | RIR databaseARIN | 2 0%low visibility |
| 2602:f92a:1320::/44 | Valid | RIR databaseARIN, RADB | 2 0%low visibility |
| 2a14:7581:fe1::/48 | Valid | RIR databaseRADB, RIPE | 2 0%low visibility |
AS-SET
AS218668'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 9 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 44.30.180.0/24 | No ROA covers it. Add a ROA for AS218668, maxLength 24. |
| Route object: RIR | 44.30.180.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS218668 whose prefix no peer sees AS218668 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2602:f92a:1321::/48 | ARIN, RADB | Valid |
| 2602:f92a:1325::/48 | ARIN, RADB | Valid |
| 2602:f92a:1326::/48 | ARIN, RADB | Valid |
| 2602:f92a:1327::/48 | ARIN, RADB | Valid |
| 2602:f92a:1328::/48 | ARIN, RADB | Valid |
| 2602:f92a:1329::/48 | ARIN, RADB | Valid |
| 2602:f92a:132a::/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.