bgpreport

Network · data from 2026-11-12

AS40289 PHX-CGIAM - CGI TECHNOLOGIES AND SOLUTIONS INC.

Registry name: PHX-CGIAM - CGI TECHNOLOGIES AND SOLUTIONS INC., US · not in PeeringDB

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

Announced routes

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

128.129.88.0/21 No ROA Other IRR onlyRADB 672 100% 67
162.70.72.0/24 No ROA Other IRR onlyALTDB 671 100% 67
208.72.60.0/24 No ROA Other IRR onlyALTDB 671 100% 67
2607:f020::/40 No ROA Other IRR onlyALTDB 635 100% 67
2607:f020:2000::/40 No ROA Other IRR onlyALTDB 633 100% 68
216.128.240.0/20 No ROA RIR databaseARIN 673 100% 67

AS-SET

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

  • ROA: none6
  • Route object: RIR5
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none128.129.88.0/21No ROA covers it. Add a ROA for AS40289, maxLength 21.672 of 673
Route object: RIR128.129.88.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none162.70.72.0/24No ROA covers it. Add a ROA for AS40289, maxLength 24.671 of 673
Route object: RIR162.70.72.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none208.72.60.0/24No ROA covers it. Add a ROA for AS40289, maxLength 24.671 of 673
Route object: RIR208.72.60.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none2607:f020::/40No ROA covers it. Add a ROA for AS40289, maxLength 40.635 of 636
Route object: RIR2607:f020::/40Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
ROA: none2607:f020:2000::/40No ROA covers it. Add a ROA for AS40289, maxLength 40.633 of 636
Route object: RIR2607:f020:2000::/40Route object only in ALTDB. Add it in the RIR database for the space.633 of 636
ROA: none216.128.240.0/20No ROA covers it. Add a ROA for AS40289, maxLength 20.673 of 673

Route objects not announced

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

192.250.1.0/24ALTDBNo ROA
192.250.5.0/24ALTDBNo ROA
205.135.144.0/23RADBNo ROA
205.135.144.0/24RADBNo ROA
205.135.145.0/24RADBNo ROA
205.135.251.0/24RADBNo 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.