bgpreport

Network · data from 2026-11-12

AS41135 Bandwidth (f/k/a Voxbone)

Registry name: VOXBONE-AS Voxbone SA, BE · PeeringDB

28IPv4 routes 100.0% RPKI valid · 53.6% with a route object
6IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 13 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS41135, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS41135, 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.

81.201.88.0/23 Valid Nonecovered by 81.201.80.0/20 673 100% 67
81.201.90.0/23 Valid Nonecovered by 81.201.80.0/20 673 100% 67
81.201.92.0/23 Valid Nonecovered by 81.201.80.0/20 673 100% 67
185.47.148.0/24 Valid Nonecovered by 185.47.148.0/22 673 100% 67
185.47.149.0/24 Valid Nonecovered by 185.47.148.0/22 673 100% 67
185.47.150.0/23 Valid Nonecovered by 185.47.148.0/22 673 100% 67
185.47.150.0/24 Valid Nonecovered by 185.47.148.0/22 673 100% 67
185.47.151.0/24 Valid Nonecovered by 185.47.148.0/22 673 100% 67
81.201.80.0/24 Valid Nonecovered by 81.201.80.0/21 672 100% 67
81.201.91.0/24 Valid Nonecovered by 81.201.80.0/20 672 100% 67
81.201.92.0/24 Valid Nonecovered by 81.201.80.0/20 672 100% 67
81.201.93.0/24 Valid Nonecovered by 81.201.80.0/20 672 100% 67
185.47.148.0/23 Valid Nonecovered by 185.47.148.0/22 672 100% 67
81.201.80.0/20 Valid RIR databaseNTTCOM, RADB, RIPE 673 100% 67
81.201.82.0/23 Valid RIR databaseNTTCOM, RIPE 673 100% 67
81.201.86.0/23 Valid RIR databaseNTTCOM, RIPE 673 100% 67
81.201.82.0/24 Valid RIR databaseNTTCOM, RIPE 672 100% 67
81.201.83.0/24 Valid RIR databaseNTTCOM, RIPE 672 100% 67
81.201.84.0/23 Valid RIR databaseNTTCOM, RADB, RIPE 672 100% 67
81.201.86.0/24 Valid RIR databaseRIPE 672 100% 67
81.201.87.0/24 Valid RIR databaseRIPE 672 100% 67
81.201.88.0/24 Valid RIR databaseRIPE 672 100% 67
81.201.90.0/24 Valid RIR databaseRIPE 672 100% 67
81.201.94.0/24 Valid RIR databaseRIPE 672 100% 67
81.201.95.0/24 Valid RIR databaseRIPE 672 100% 67
81.201.89.0/24 Valid RIR databaseNTTCOM, RIPE 671 100% 67
81.201.84.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 670 100% 67
81.201.85.0/24 Valid RIR databaseRIPE 670 100% 67
2a03:b500::/32 Valid RIR databaseRIPE 636 100% 67
2a03:b500::/35 Valid RIR databaseRIPE 636 100% 67
2a03:b500::/41 Valid RIR databaseRIPE 636 100% 67
2a03:b500::/48 Valid RIR databaseRIPE 636 100% 67
2a03:b500:80::/41 Valid RIR databaseRIPE 636 100% 67
2a03:b500:80::/48 Valid RIR databaseRIPE 636 100% 67

AS-SET

AS41135's PeeringDB record names no 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 27 are in fix.csv.

  • Route object: none13
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
Route object: none81.201.88.0/23No route object for it. A route object for 81.201.80.0/20 with origin AS41135 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41135 in the RIR database for the space.673 of 673
Route object: none81.201.90.0/23No route object for it. A route object for 81.201.80.0/20 with origin AS41135 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41135 in the RIR database for the space.673 of 673
Route object: none81.201.92.0/23No route object for it. A route object for 81.201.80.0/20 with origin AS41135 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41135 in the RIR database for the space.673 of 673
Route object: none185.47.148.0/24No route object for it. A route object for 185.47.148.0/22 with origin AS41135 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41135 in the RIR database for the space.673 of 673
Route object: none185.47.149.0/24No route object for it. A route object for 185.47.148.0/22 with origin AS41135 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41135 in the RIR database for the space.673 of 673
Route object: none185.47.150.0/23No route object for it. A route object for 185.47.148.0/22 with origin AS41135 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41135 in the RIR database for the space.673 of 673
Route object: none185.47.150.0/24No route object for it. A route object for 185.47.148.0/22 with origin AS41135 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41135 in the RIR database for the space.673 of 673
Route object: none185.47.151.0/24No route object for it. A route object for 185.47.148.0/22 with origin AS41135 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41135 in the RIR database for the space.673 of 673
Route object: none81.201.80.0/24No route object for it. A route object for 81.201.80.0/21 with origin AS41135 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41135 in the RIR database for the space.672 of 673
Route object: none81.201.91.0/24No route object for it. A route object for 81.201.80.0/20 with origin AS41135 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41135 in the RIR database for the space.672 of 673
Route object: none81.201.92.0/24No route object for it. A route object for 81.201.80.0/20 with origin AS41135 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41135 in the RIR database for the space.672 of 673
Route object: none81.201.93.0/24No route object for it. A route object for 81.201.80.0/20 with origin AS41135 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41135 in the RIR database for the space.672 of 673
Route object: none185.47.148.0/23No route object for it. A route object for 185.47.148.0/22 with origin AS41135 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41135 in the RIR database for the space.672 of 673

Route objects not announced

Route objects with origin AS41135 whose prefix no peer sees AS41135 announce. Many are kept on purpose (backup routes, space announced only in some places).

81.201.80.0/21NTTCOM, RIPEValid
81.201.81.0/24RIPEValid
185.47.148.0/22RIPEValid
2a03:b500:2000::/35RIPEValid
2a03:b500:2000::/41RIPEValid
2a03:b500:2000::/48RIPEValid
2a03:b500:2001::/48RIPEValid
2a03:b500:4000::/35RIPEValid
2a03:b500:4000::/41RIPEValid
2a03:b500:4000::/48RIPEValid
2a03:b500:4080::/41RIPEValid
2a03:b500:4080::/48RIPEValid
2a03:b500:c000::/35RIPEValid
2a03:b500:c000::/48RIPEValid

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.