Network · data from 2026-11-12
AS42160 LCPDCO DC STAR nv
Registry name: LCPDCO DC STAR nv, BE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS42160, 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.
| 185.49.180.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 185.55.92.0/23 | Valid | Nonecovered by 185.55.92.0/22 | 672 100% |
| 2a02:5940:4000::/34 | Valid | Nonecovered by 2a02:5940::/32 | 635 100% |
| 81.95.112.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 81.95.112.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 81.95.118.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 81.95.120.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 81.95.122.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 91.206.84.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 91.234.203.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 151.240.77.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 158.173.128.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 164.138.104.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 185.18.148.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 185.19.180.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.55.92.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 193.110.248.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 193.110.250.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 193.110.252.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 195.225.220.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.225.221.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.225.222.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 81.95.116.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 81.95.117.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a02:5940::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a04:b80:1::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS42160 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: none1
- Route object: none2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.49.180.0/22 | No ROA covers it. Add a ROA for AS42160, maxLength 22. |
| Route object: none | 185.55.92.0/23 | No route object for it. A route object for 185.55.92.0/22 with origin AS42160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42160 in the RIR database for the space. |
| Route object: none | 2a02:5940:4000::/34 | No route object for it. A route object for 2a02:5940::/32 with origin AS42160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42160 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS42160 whose prefix no peer sees AS42160 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 81.95.124.0/22 | RIPE | Valid |
| 91.230.64.0/24 | RIPE | Valid |
| 185.48.12.0/24 | RIPE | No ROA |
| 193.110.248.0/21 | RIPE | Valid |
| 2a01:9960::/32 | RIPE | 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.