Network · data from 2026-11-12
AS41041 Conversant Europe
Registry name: VCLK-EU-SE Conversant LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS41041, 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.
| 63.215.202.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 64.158.223.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 2a02:fa8:1c10::/44 | No ROA | Other IRR onlyRADB | 635 100% |
| 2a02:fa8:8800::/40 | No ROA | Other IRR onlyRADB | 635 100% |
| 89.207.16.0/21 | No ROA | RIR databaseRADB, RIPE | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS41041: RADB::AS-CNVR. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS41041 isn't in the set, or no route object for AS41041 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS41041 in it | Not covered |
|---|---|---|---|---|---|
| RADB::AS-CNVR | RADB | 5 | 1 | Yes | 0 |
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 11 are in fix.csv.
- ROA: none5
- Route object: RIR4
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 63.215.202.0/24 | No ROA covers it. Add a ROA for AS41041, maxLength 24. |
| Route object: RIR | 63.215.202.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 64.158.223.0/24 | No ROA covers it. Add a ROA for AS41041, maxLength 24. |
| Route object: RIR | 64.158.223.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2a02:fa8:1c10::/44 | No ROA covers it. Add a ROA for AS41041, maxLength 44. |
| Route object: RIR | 2a02:fa8:1c10::/44 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2a02:fa8:8800::/40 | No ROA covers it. Add a ROA for AS41041, maxLength 40. |
| Route object: RIR | 2a02:fa8:8800::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 89.207.16.0/21 | No ROA covers it. Add a ROA for AS41041, maxLength 21. |
Route objects not announced
Route objects with origin AS41041 whose prefix no peer sees AS41041 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 159.127.107.0/24 | RADB | No ROA |
| 2606:ae80::/44 | 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.