bgpreport

Network · data from 2026-11-12

AS397433 Great-West Life Assurance Company

Registry name: GWL-CA-ASN - The Great-West Life Assurance Company, CA · PeeringDB

11IPv4 routes 0.0% RPKI valid · 72.7% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
11No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS397433, seen from no peer

Announced routes

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

156.11.159.0/24 No ROA Nonecovered by 156.11.128.0/19 673 100% 67
156.11.16.0/22 No ROA Other origin onlycovered by 156.11.0.0/16 671 100% 67
156.11.20.0/23 No ROA Other origin onlycovered by 156.11.0.0/16 671 100% 67
156.11.0.0/22 No ROA Other IRR onlyRADB 673 100% 67
156.11.128.0/19 No ROA Other IRR onlyRADB 673 100% 67
156.11.160.0/21 No ROA Other IRR onlyRADB 673 100% 67
156.11.226.0/24 No ROA Other IRR onlyRADB 673 100% 67
198.96.223.0/24 No ROA Other IRR onlyRADB 673 100% 67
156.11.8.0/22 No ROA Other IRR onlyRADB 671 100% 67
156.11.12.0/23 No ROA Other IRR onlyRADB 671 100% 67
192.197.253.0/24 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

PeeringDB's irr_as_set for AS397433: AS-DC-PEER. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS397433 isn't in the set, or no route object for AS397433 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS397433 in itNot covered
AS-DC-PEER In no IRR database read today.

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

  • ROA: none11
  • Route object: none3
  • Route object: RIR8
  • AS-SET: not found1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none156.11.159.0/24No ROA covers it. Add a ROA for AS397433, maxLength 24.673 of 673
Route object: none156.11.159.0/24No route object for it. A route object for 156.11.128.0/19 with origin AS397433 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397433 in the RIR database for the space.673 of 673
ROA: none156.11.16.0/22No ROA covers it. Add a ROA for AS397433, maxLength 22.671 of 673
Route object: none156.11.16.0/22Route objects for it name AS6327. A route object for 156.11.0.0/16 with origin AS397433 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397433 in the RIR database for the space.671 of 673
ROA: none156.11.20.0/23No ROA covers it. Add a ROA for AS397433, maxLength 23.671 of 673
Route object: none156.11.20.0/23Route objects for it name AS1273. A route object for 156.11.0.0/16 with origin AS397433 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397433 in the RIR database for the space.671 of 673
ROA: none156.11.0.0/22No ROA covers it. Add a ROA for AS397433, maxLength 22.673 of 673
Route object: RIR156.11.0.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none156.11.128.0/19No ROA covers it. Add a ROA for AS397433, maxLength 19.673 of 673
Route object: RIR156.11.128.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none156.11.160.0/21No ROA covers it. Add a ROA for AS397433, maxLength 21.673 of 673
Route object: RIR156.11.160.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none156.11.226.0/24No ROA covers it. Add a ROA for AS397433, maxLength 24.673 of 673
Route object: RIR156.11.226.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none198.96.223.0/24No ROA covers it. Add a ROA for AS397433, maxLength 24.673 of 673
Route object: RIR198.96.223.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none156.11.8.0/22No ROA covers it. Add a ROA for AS397433, maxLength 22.671 of 673
Route object: RIR156.11.8.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none156.11.12.0/23No ROA covers it. Add a ROA for AS397433, maxLength 23.671 of 673
Route object: RIR156.11.12.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none192.197.253.0/24No ROA covers it. Add a ROA for AS397433, maxLength 24.671 of 673
Route object: RIR192.197.253.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
AS-SET: not foundAS-DC-PEERPeeringDB names AS-DC-PEER; no IRR database read has it.

Route objects not announced

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

156.11.0.0/16RADBNo ROA
156.11.128.0/18RADBNo 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.