bgpreport

Network · data from 2026-11-12

AS327896 BIZVOIP - BIZVOIP

Registry name: BIZVOIP - BIZVOIP, ZA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS327896, 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.
169.255.240.0/23 Valid Nonecovered by 169.255.240.0/22 672 100% 66
169.255.242.0/23 Valid Nonecovered by 169.255.240.0/22 672 100% 66
169.255.240.0/24 Valid Nonecovered by 169.255.240.0/22 64 10%low visibility 21
169.255.241.0/24 Valid Nonecovered by 169.255.240.0/22 64 10%low visibility 21
169.255.242.0/24 Valid Nonecovered by 169.255.240.0/22 64 10%low visibility 21
169.255.243.0/24 Valid Nonecovered by 169.255.240.0/22 64 10%low visibility 21
102.223.236.0/22 Valid RIR databaseAFRINIC 673 100% 66
169.255.240.0/22 Valid RIR databaseAFRINIC, RIPE-NONAUTH 672 100% 66

AS-SET

AS327896 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 12 are in fix.csv.

  • Route object: none6
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: none169.255.240.0/23No route object for it. A route object for 169.255.240.0/22 with origin AS327896 covers it (filters allowing more-specifics accept it). Add a route object with origin AS327896 in the RIR database for the space.672 of 673
Route object: none169.255.242.0/23No route object for it. A route object for 169.255.240.0/22 with origin AS327896 covers it (filters allowing more-specifics accept it). Add a route object with origin AS327896 in the RIR database for the space.672 of 673
Route object: none169.255.240.0/24No route object for it. A route object for 169.255.240.0/22 with origin AS327896 covers it (filters allowing more-specifics accept it). Add a route object with origin AS327896 in the RIR database for the space.64 of 673
Route object: none169.255.241.0/24No route object for it. A route object for 169.255.240.0/22 with origin AS327896 covers it (filters allowing more-specifics accept it). Add a route object with origin AS327896 in the RIR database for the space.64 of 673
Route object: none169.255.242.0/24No route object for it. A route object for 169.255.240.0/22 with origin AS327896 covers it (filters allowing more-specifics accept it). Add a route object with origin AS327896 in the RIR database for the space.64 of 673
Route object: none169.255.243.0/24No route object for it. A route object for 169.255.240.0/22 with origin AS327896 covers it (filters allowing more-specifics accept it). Add a route object with origin AS327896 in the RIR database for the space.64 of 673

Route objects not announced

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

102.223.236.0/23AFRINICValid
102.223.236.0/24AFRINICValid
102.223.237.0/24AFRINICValid
102.223.238.0/23AFRINICValid
102.223.238.0/24AFRINICValid
102.223.239.0/24AFRINICValid

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.