Network · data from 2026-11-12
AS21641
Not in the RIR AS name list · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS21641, 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.
| 2607:8bc0::/32 | No ROA | None | 52 8%low visibility |
| 206.206.103.0/24 | Valid | Other IRR onlyRADB | 6 1%low visibility |
| 194.147.71.0/24 | Valid | RIR databaseRIPE | 6 1%low visibility |
AS-SET
AS21641 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.
- ROA: none1
- Route object: none1
- Route object: RIR1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2607:8bc0::/32 | No ROA covers it. Add a ROA for AS21641, maxLength 32. |
| Route object: none | 2607:8bc0::/32 | No route object for it. Add a route object with origin AS21641 in the RIR database for the space. |
| Route object: RIR | 206.206.103.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS21641 whose prefix no peer sees AS21641 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 199.231.70.0/24 | ARIN, RADB | Valid |
| 216.75.145.0/24 | RADB | Valid |
| 2a06:de01:100::/44 | RIPE | No ROA |
| 2a0f:9400:7389::/48 | RIPE | 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.