Network · data from 2026-11-12
AS216043
Not in the RIR AS name list · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS216043, 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.
| 46.203.125.0/24 | Invalid: origin | None | 4 1%low visibility |
| 185.2.162.0/24 | Invalid: origin | None | 4 1%low visibility |
| 185.2.163.0/24 | Invalid: origin | None | 4 1%low visibility |
| 46.203.124.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
AS-SET
AS216043 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: origin4
- Route object: none4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 46.203.125.0/24 | ROAs covering it name AS834, not AS216043. If AS216043 should announce it, add a ROA for AS216043. |
| Route object: none | 46.203.125.0/24 | No route object for it. Add a route object with origin AS216043 in the RIR database for the space. |
| ROA: origin | 185.2.162.0/24 | ROAs covering it name AS4766, AS9304, not AS216043. If AS216043 should announce it, add a ROA for AS216043. |
| Route object: none | 185.2.162.0/24 | No route object for it. Add a route object with origin AS216043 in the RIR database for the space. |
| ROA: origin | 185.2.163.0/24 | ROAs covering it name AS4766, AS9304, not AS216043. If AS216043 should announce it, add a ROA for AS216043. |
| Route object: none | 185.2.163.0/24 | No route object for it. Add a route object with origin AS216043 in the RIR database for the space. |
| ROA: origin | 46.203.124.0/24 | ROAs covering it name AS834, AS20473, not AS216043. If AS216043 should announce it, add a ROA for AS216043. |
| Route object: none | 46.203.124.0/24 | Route objects for it name AS834, AS20473. Add a route object with origin AS216043 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS216043 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.