Network · data from 2026-11-12
AS12798 VCW-AS BV Gaming Limited
Registry name: VCW-AS BV Gaming Limited, GI · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS12798, 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.
| 212.22.248.0/24 | Valid | Nonecovered by 212.22.224.0/19 | 672 100% |
| 212.22.249.0/24 | Valid | Nonecovered by 212.22.224.0/19 | 672 100% |
| 212.22.251.0/24 | Valid | Nonecovered by 212.22.224.0/19 | 672 100% |
| 212.22.235.0/24 | Valid | Nonecovered by 212.22.224.0/19 | 671 100% |
| 212.22.250.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 185.82.50.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 212.22.228.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 212.22.229.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 212.22.230.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 212.22.232.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 212.22.233.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 212.22.234.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.82.51.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.22.231.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.22.224.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 212.22.225.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 212.22.226.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 212.22.227.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS12798 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 21 are in fix.csv.
- Route object: none4
- Route object: RIR1
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 212.22.248.0/24 | No route object for it. A route object for 212.22.224.0/19 with origin AS12798 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12798 in the RIR database for the space. |
| Route object: none | 212.22.249.0/24 | No route object for it. A route object for 212.22.224.0/19 with origin AS12798 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12798 in the RIR database for the space. |
| Route object: none | 212.22.251.0/24 | No route object for it. A route object for 212.22.224.0/19 with origin AS12798 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12798 in the RIR database for the space. |
| Route object: none | 212.22.235.0/24 | No route object for it. A route object for 212.22.224.0/19 with origin AS12798 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12798 in the RIR database for the space. |
| Route object: RIR | 212.22.250.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS12798 whose prefix no peer sees AS12798 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.82.48.0/24 | RIPE | Valid |
| 212.22.224.0/19 | RIPE | Valid |
| 212.22.224.0/21 | RIPE | Valid |
| 212.22.230.0/23 | RIPE | Valid |
| 212.22.239.0/24 | RIPE | Valid |
| 212.22.240.0/24 | NTTCOM, RADB, RIPE | Valid |
| 212.22.241.0/24 | RIPE | Valid |
| 212.22.242.0/24 | RIPE | Valid |
| 212.22.243.0/24 | RIPE | Valid |
| 212.22.244.0/24 | RIPE | Valid |
| 212.22.245.0/24 | RIPE | Valid |
| 212.22.246.0/24 | RIPE | Valid |
| 212.22.247.0/24 | RIPE | Valid |
| 212.22.253.0/24 | NTTCOM, RADB, RIPE | Valid |
| 212.22.254.0/24 | RIPE | Valid |
| 212.22.255.0/24 | RIPE | Valid |
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.