bgpreport

Network · data from 2026-11-12

AS22711 GNA-CORP-GENWORTH-FINANCIAL - Genworth North America Corporation

Registry name: GNA-CORP-GENWORTH-FINANCIAL - Genworth North America Corporation, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22711, 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.
206.83.160.0/21 Valid Nonecovered by 206.83.160.0/20 673 100% 67
206.83.166.0/23 Valid Nonecovered by 206.83.160.0/20 673 100% 67
206.83.168.0/21 Valid Nonecovered by 206.83.160.0/20 673 100% 67
2620:13d:f002::/47 Valid Nonecovered by 2620:13d:f000::/40 636 100% 67
2620:13d:f000::/47 Valid Nonecovered by 2620:13d:f000::/40 634 100% 68
206.83.160.0/20 Valid Other IRR onlyRADB 673 100% 67
2620:13d:f000::/40 Valid Other IRR onlyRADB 634 100% 68

AS-SET

AS22711 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: none5
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none206.83.160.0/21No route object for it. A route object for 206.83.160.0/20 with origin AS22711 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22711 in the RIR database for the space.673 of 673
Route object: none206.83.166.0/23No route object for it. A route object for 206.83.160.0/20 with origin AS22711 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22711 in the RIR database for the space.673 of 673
Route object: none206.83.168.0/21No route object for it. A route object for 206.83.160.0/20 with origin AS22711 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22711 in the RIR database for the space.673 of 673
Route object: none2620:13d:f002::/47No route object for it. A route object for 2620:13d:f000::/40 with origin AS22711 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22711 in the RIR database for the space.636 of 636
Route object: none2620:13d:f000::/47No route object for it. A route object for 2620:13d:f000::/40 with origin AS22711 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22711 in the RIR database for the space.634 of 636
Route object: RIR206.83.160.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2620:13d:f000::/40Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

2620:34::/48RADBNo ROA

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.