Network · data from 2026-11-12
AS396169
Not in the RIR AS name list · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS396169, 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.
| 12.172.75.0/24 | No ROA | None | 673 100% |
| 2605:aac0::/32 | No ROA | Other IRR onlyRADB | 635 100% |
AS-SET
AS396169 isn't in PeeringDB, where networks name their 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 6 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 12.172.75.0/24 | No ROA covers it. Add a ROA for AS396169, maxLength 24. |
| Route object: none | 12.172.75.0/24 | No route object for it. Add a route object with origin AS396169 in the RIR database for the space. |
| ROA: none | 2605:aac0::/32 | No ROA covers it. Add a ROA for AS396169, maxLength 32. |
| Route object: RIR | 2605:aac0::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS396169 whose prefix no peer sees AS396169 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.155.208.0/24 | RADB | No ROA |
| 23.155.209.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.