Network · data from 2026-11-12
AS51905 CWCS-VM Compuweb Communications Services Limited
Registry name: CWCS-VM Compuweb Communications Services Limited, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51905, 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.
| 84.19.112.0/24 | Valid | Nonecovered by 84.19.112.0/21 | 673 100% |
| 84.19.113.0/24 | Valid | Other origin onlycovered by 84.19.112.0/21 | 673 100% |
| 84.19.114.0/24 | Valid | Other origin onlycovered by 84.19.112.0/21 | 673 100% |
| 84.19.115.0/24 | Valid | Nonecovered by 84.19.112.0/21 | 673 100% |
| 84.19.116.0/24 | Valid | Nonecovered by 84.19.112.0/21 | 673 100% |
| 84.19.117.0/24 | Valid | Nonecovered by 84.19.112.0/21 | 673 100% |
| 84.19.118.0/24 | Valid | Nonecovered by 84.19.112.0/21 | 673 100% |
| 84.19.119.0/24 | Valid | Nonecovered by 84.19.112.0/21 | 673 100% |
| 84.19.112.0/21 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS51905 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.
- Route object: none8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 84.19.112.0/24 | No route object for it. A route object for 84.19.112.0/21 with origin AS51905 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51905 in the RIR database for the space. |
| Route object: none | 84.19.113.0/24 | Route objects for it name AS15510. A route object for 84.19.112.0/21 with origin AS51905 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51905 in the RIR database for the space. |
| Route object: none | 84.19.114.0/24 | Route objects for it name AS15510. A route object for 84.19.112.0/21 with origin AS51905 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51905 in the RIR database for the space. |
| Route object: none | 84.19.115.0/24 | No route object for it. A route object for 84.19.112.0/21 with origin AS51905 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51905 in the RIR database for the space. |
| Route object: none | 84.19.116.0/24 | No route object for it. A route object for 84.19.112.0/21 with origin AS51905 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51905 in the RIR database for the space. |
| Route object: none | 84.19.117.0/24 | No route object for it. A route object for 84.19.112.0/21 with origin AS51905 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51905 in the RIR database for the space. |
| Route object: none | 84.19.118.0/24 | No route object for it. A route object for 84.19.112.0/21 with origin AS51905 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51905 in the RIR database for the space. |
| Route object: none | 84.19.119.0/24 | No route object for it. A route object for 84.19.112.0/21 with origin AS51905 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51905 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS51905 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.