Network · data from 2026-11-12
AS18563 CGINET-01 - CGI Inc.
Registry name: CGINET-01 - CGI Inc., CA · not in PeeringDB
18IPv4 routes
27.8% RPKI valid · 61.1% with a route object
1IPv6 routes
0.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
14No ROA
7 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
16Route objects not announced
registered with origin AS18563, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS18563, 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.
| 64.254.21.0/24 | No ROA | Nonecovered by 64.254.0.0/19 | 673 100% |
| 64.254.11.0/24 | No ROA | Nonecovered by 64.254.0.0/19 | 672 100% |
| 64.254.24.0/24 | No ROA | Nonecovered by 64.254.24.0/23 | 672 100% |
| 64.254.10.0/24 | No ROA | Nonecovered by 64.254.0.0/19 | 671 100% |
| 2620:10:8000::/44 | No ROA | Other IRR onlyBELL | 635 100% |
| 64.254.6.0/23 | No ROA | RIR databaseARIN | 672 100% |
| 64.254.28.0/23 | No ROA | RIR databaseARIN | 672 100% |
| 64.254.30.0/23 | No ROA | RIR databaseARIN | 672 100% |
| 128.129.38.0/23 | No ROA | RIR databaseARIN | 672 100% |
| 128.129.40.0/21 | No ROA | RIR databaseARIN | 672 100% |
| 204.107.153.0/24 | No ROA | RIR databaseARIN | 672 100% |
| 64.254.0.0/19 | No ROA | RIR databaseARIN, BELL | 671 100% |
| 128.129.34.0/23 | No ROA | RIR databaseARIN, BELL | 671 100% |
| 128.129.48.0/20 | No ROA | RIR databaseARIN, BELL | 671 100% |
| 159.18.53.0/24 | Valid | Other origin only | 672 100% |
| 159.18.220.0/23 | Valid | None | 672 100% |
| 207.245.13.0/24 | Valid | None | 672 100% |
| 66.110.6.0/23 | Valid | Other IRR onlyBELL, RADB | 671 100% |
| 64.86.140.0/23 | Valid | RIR databaseARIN, BELL | 671 100% |
AS-SET
AS18563 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 39 are in fix.csv.
- ROA: none14
- Route object: none7
- Route object: RIR2
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.254.21.0/24 | No ROA covers it. Add a ROA for AS18563, maxLength 24. |
| Route object: none | 64.254.21.0/24 | No route object for it. A route object for 64.254.0.0/19 with origin AS18563 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18563 in the RIR database for the space. |
| ROA: none | 64.254.11.0/24 | No ROA covers it. Add a ROA for AS18563, maxLength 24. |
| Route object: none | 64.254.11.0/24 | No route object for it. A route object for 64.254.0.0/19 with origin AS18563 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18563 in the RIR database for the space. |
| ROA: none | 64.254.24.0/24 | No ROA covers it. Add a ROA for AS18563, maxLength 24. |
| Route object: none | 64.254.24.0/24 | No route object for it. A route object for 64.254.24.0/23 with origin AS18563 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18563 in the RIR database for the space. |
| ROA: none | 64.254.10.0/24 | No ROA covers it. Add a ROA for AS18563, maxLength 24. |
| Route object: none | 64.254.10.0/24 | No route object for it. A route object for 64.254.0.0/19 with origin AS18563 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18563 in the RIR database for the space. |
| ROA: none | 2620:10:8000::/44 | No ROA covers it. Add a ROA for AS18563, maxLength 44. |
| Route object: RIR | 2620:10:8000::/44 | Route object only in BELL. Add it in the RIR database for the space. |
| ROA: none | 64.254.6.0/23 | No ROA covers it. Add a ROA for AS18563, maxLength 23. |
| ROA: none | 64.254.28.0/23 | No ROA covers it. Add a ROA for AS18563, maxLength 23. |
| ROA: none | 64.254.30.0/23 | No ROA covers it. Add a ROA for AS18563, maxLength 23. |
| ROA: none | 128.129.38.0/23 | No ROA covers it. Add a ROA for AS18563, maxLength 23. |
| ROA: none | 128.129.40.0/21 | No ROA covers it. Add a ROA for AS18563, maxLength 21. |
| ROA: none | 204.107.153.0/24 | No ROA covers it. Add a ROA for AS18563, maxLength 24. |
| ROA: none | 64.254.0.0/19 | No ROA covers it. Add a ROA for AS18563, maxLength 19. |
| ROA: none | 128.129.34.0/23 | No ROA covers it. Add a ROA for AS18563, maxLength 23. |
| ROA: none | 128.129.48.0/20 | No ROA covers it. Add a ROA for AS18563, maxLength 20. |
| Route object: none | 159.18.53.0/24 | Route objects for it name AS19086. Add a route object with origin AS18563 in the RIR database for the space. |
| Route object: none | 159.18.220.0/23 | No route object for it. Add a route object with origin AS18563 in the RIR database for the space. |
| Route object: none | 207.245.13.0/24 | No route object for it. Add a route object with origin AS18563 in the RIR database for the space. |
| Route object: RIR | 66.110.6.0/23 | Route object only in BELL, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18563 whose prefix no peer sees AS18563 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.254.24.0/22 | RADB | No ROA |
| 64.254.24.0/23 | RADB | No ROA |
| 128.129.96.0/23 | ALTDB | No ROA |
| 142.101.0.0/16 | BELL | No ROA |
| 192.82.117.0/24 | ALTDB | No ROA |
| 192.250.2.0/24 | ALTDB, BELL | No ROA |
| 192.250.3.0/24 | ALTDB | No ROA |
| 192.250.4.0/24 | ALTDB | No ROA |
| 198.34.224.0/24 | BELL | No ROA |
| 199.84.232.0/22 | BELL | No ROA |
| 199.84.233.0/24 | BELL | No ROA |
| 199.84.234.0/23 | BELL | No ROA |
| 199.84.236.0/23 | BELL | No ROA |
| 205.135.248.0/21 | BELL | No ROA |
| 2600:b800::/28 | ARIN | No ROA |
| 2620:10:8000::/48 | ALTDB | No 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.