Announced routes
Every prefix a peer of the route collectors sees with origin AS399980, 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.
| 2602:fd10:e00::/48 | Valid | Nonecovered by 2602:fd10:e00::/40 | 635 100% |
| 2602:fd10:f0::/48 | Valid | RIR databaseARIN, RADB | 634 100% |
| 2602:fd10:e00::/40 | Valid | RIR databaseARIN, RADB | 633 100% |
AS-SET
AS399980'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 2 are in fix.csv.
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2602:fd10:e00::/48 | No route object for it. A route object for 2602:fd10:e00::/40 with origin AS399980 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399980 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS399980 whose prefix no peer sees AS399980 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.164.145.0/24 | 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.