Network · data from 2026-11-12
AS64401 RIGNET-GB-AS Rignet AS
Registry name: RIGNET-GB-AS Rignet AS, NO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS64401, 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.
| 89.251.208.0/20 | No ROA | RIR databaseRIPE | 671 100% |
| 109.71.144.0/21 | No ROA | RIR databaseRIPE | 671 100% |
| 178.20.108.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 2a00:ed20::/32 | No ROA | RIR databaseRIPE | 635 100% |
| 2a04:4900::/29 | No ROA | RIR databaseRIPE | 634 100% |
AS-SET
AS64401 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 8 are in fix.csv.
- ROA: none5
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 89.251.208.0/20 | No ROA covers it. Add a ROA for AS64401, maxLength 20. |
| ROA: none | 109.71.144.0/21 | No ROA covers it. Add a ROA for AS64401, maxLength 21. |
| ROA: none | 178.20.108.0/22 | No ROA covers it. Add a ROA for AS64401, maxLength 22. |
| ROA: none | 2a00:ed20::/32 | No ROA covers it. Add a ROA for AS64401, maxLength 32. |
| ROA: none | 2a04:4900::/29 | No ROA covers it. Add a ROA for AS64401, maxLength 29. |
Route objects not announced
Route objects with origin AS64401 whose prefix no peer sees AS64401 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 178.20.104.0/21 | RIPE | No ROA |
| 178.20.110.0/24 | RIPE | No ROA |
| 2001:470:2b2::/48 | ARIN | 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.