Network · data from 2026-11-12
AS214546
Not in the RIR AS name list · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS214546, 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.
| 2a0d:d900::/32 | Invalid: origin | Other origin only | 2 0%low visibility |
| 2a09:54c2::/32 | Invalid: origin | Other origin only | 1 0%low visibility |
AS-SET
AS214546 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 4 are in fix.csv.
- ROA: origin2
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a0d:d900::/32 | ROAs covering it name AS207196, not AS214546. If AS214546 should announce it, add a ROA for AS214546. |
| Route object: none | 2a0d:d900::/32 | Route objects for it name AS207196. Add a route object with origin AS214546 in the RIR database for the space. |
| ROA: origin | 2a09:54c2::/32 | ROAs covering it name AS55201, not AS214546. If AS214546 should announce it, add a ROA for AS214546. |
| Route object: none | 2a09:54c2::/32 | Route objects for it name AS55201. Add a route object with origin AS214546 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS214546 is announced.
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.