Network · data from 2026-11-12
AS269384
Not in the RIR AS name list · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269384, 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.
| 2804:63cc::/32 | Valid | Other IRR onlyALTDB, RADB | 634 100% |
AS-SET
AS269384 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 7 are in fix.csv.
- Route object: RIR1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 2804:63cc::/32 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269384 whose prefix no peer sees AS269384 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:63cc::/33 | RADB | Valid |
| 2804:63cc:8000::/33 | RADB | Valid |
| 2804:63cc:c000::/34 | RADB | Valid |
| 2804:63cc:f200::/40 | RADB | Valid |
| 2804:63cc:fa00::/44 | RADB | Valid |
| 2804:63cc:ff00::/40 | 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.