Network · data from 2026-11-12
AS206161 Nils Steinger
Registry name: voidptr Val Steinger, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS206161, 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.
| 2a0e:46c6:160::/44 | No ROA | Nonecovered by 2a0e:46c6:100::/40 | 633 100% |
| 44.31.160.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 2001:678:c88::/48 | Valid | RIR databaseRADB, RIPE | 636 100% |
AS-SET
AS206161's PeeringDB record names no 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: none2
- Route object: none1
- Route object: RIR1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a0e:46c6:160::/44 | No ROA covers it. Add a ROA for AS206161, maxLength 44. |
| Route object: none | 2a0e:46c6:160::/44 | No route object for it. A route object for 2a0e:46c6:100::/40 with origin AS206161 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206161 in the RIR database for the space. |
| ROA: none | 44.31.160.0/24 | No ROA covers it. Add a ROA for AS206161, maxLength 24. |
| Route object: RIR | 44.31.160.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS206161 whose prefix no peer sees AS206161 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:678:10f4::/48 | RIPE | Valid |
| 2a0e:46c6:100::/40 | RADB, RIPE | No ROA |
| 2a0e:46c6:160::/48 | RIPE | No ROA |
| 2a0e:8f00:8000::/40 | RADB | No ROA |
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.