Network · data from 2026-11-12
AS328459 VBN Services - VBN Services
Registry name: VBN Services - VBN Services, BW · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS328459, 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.
| 41.76.240.0/24 | Valid | Nonecovered by 41.76.240.0/21 | 673 100% |
| 41.76.241.0/24 | Valid | Nonecovered by 41.76.240.0/21 | 673 100% |
| 41.76.242.0/24 | Valid | Nonecovered by 41.76.240.0/21 | 673 100% |
| 41.76.243.0/24 | Valid | Nonecovered by 41.76.240.0/21 | 673 100% |
| 41.76.244.0/24 | Valid | Nonecovered by 41.76.240.0/21 | 673 100% |
| 41.76.245.0/24 | Valid | Nonecovered by 41.76.240.0/21 | 673 100% |
| 41.76.246.0/24 | Valid | Nonecovered by 41.76.240.0/21 | 673 100% |
| 41.76.247.0/24 | Valid | Nonecovered by 41.76.240.0/21 | 673 100% |
| 83.143.27.0/24 | Valid | Nonecovered by 83.143.24.0/21 | 672 100% |
| 41.216.208.0/21 | Valid | RIR databaseAFRINIC | 671 100% |
| 83.143.24.0/21 | Valid | RIR databaseAFRINIC | 671 100% |
| 156.38.16.0/20 | Valid | RIR databaseAFRINIC | 671 100% |
AS-SET
AS328459 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 10 are in fix.csv.
- Route object: none9
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 41.76.240.0/24 | No route object for it. A route object for 41.76.240.0/21 with origin AS328459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328459 in the RIR database for the space. |
| Route object: none | 41.76.241.0/24 | No route object for it. A route object for 41.76.240.0/21 with origin AS328459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328459 in the RIR database for the space. |
| Route object: none | 41.76.242.0/24 | No route object for it. A route object for 41.76.240.0/21 with origin AS328459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328459 in the RIR database for the space. |
| Route object: none | 41.76.243.0/24 | No route object for it. A route object for 41.76.240.0/21 with origin AS328459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328459 in the RIR database for the space. |
| Route object: none | 41.76.244.0/24 | No route object for it. A route object for 41.76.240.0/21 with origin AS328459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328459 in the RIR database for the space. |
| Route object: none | 41.76.245.0/24 | No route object for it. A route object for 41.76.240.0/21 with origin AS328459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328459 in the RIR database for the space. |
| Route object: none | 41.76.246.0/24 | No route object for it. A route object for 41.76.240.0/21 with origin AS328459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328459 in the RIR database for the space. |
| Route object: none | 41.76.247.0/24 | No route object for it. A route object for 41.76.240.0/21 with origin AS328459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328459 in the RIR database for the space. |
| Route object: none | 83.143.27.0/24 | No route object for it. A route object for 83.143.24.0/21 with origin AS328459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328459 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS328459 whose prefix no peer sees AS328459 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 41.76.240.0/21 | AFRINIC | 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.