bgpreport

Network · data from 2026-11-12

AS54643 Idigital Internet

Registry name: IDIGITAL - Idigital Internet Inc., CA · PeeringDB

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

Announced routes

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

69.90.223.0/24 No ROA Other IRR onlyRADB 673 100% 70
69.90.243.0/24 No ROA Other IRR onlyRADB 673 100% 70
70.33.247.0/24 No ROA Other IRR onlyRADB 673 100% 70
107.6.27.0/24 No ROA Other IRR onlyRADB 673 100% 70
64.69.79.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
107.6.20.0/23 No ROA Other IRR onlyRADB 2 0%low visibility 2
23.111.72.0/23 Valid Nonecovered by 23.111.64.0/20 673 100% 70
23.111.74.0/23 Valid Nonecovered by 23.111.64.0/20 673 100% 70
67.231.16.0/21 Valid Nonecovered by 67.231.16.0/20 673 100% 70
64.34.70.0/24 Valid Other IRR onlyRADB 673 100% 70
64.34.72.0/24 Valid Other IRR onlyRADB 673 100% 70
67.231.24.0/22 Valid Other IRR onlyRADB 673 100% 70
67.231.28.0/23 Valid Other IRR onlyRADB 673 100% 70
67.231.30.0/23 Valid Other IRR onlyRADB 673 100% 70
104.36.148.0/23 Valid Other IRR onlyRADB 673 100% 70
104.36.150.0/23 Valid Other IRR onlyRADB 673 100% 70
23.111.64.0/22 Valid RIR databaseARIN, RADB 673 100% 70
23.111.68.0/22 Valid RIR databaseARIN 673 100% 70
66.85.28.0/23 Valid RIR databaseARIN 673 100% 70
66.85.30.0/23 Valid RIR databaseARIN 673 100% 70
104.193.172.0/23 Valid RIR databaseARIN 673 100% 70
104.193.174.0/23 Valid RIR databaseARIN 673 100% 70
2607:7b00:3000::/36 Valid RIR databaseARIN 635 100% 69
2607:7b00:4000::/36 Valid RIR databaseARIN 635 100% 67
2607:7b00:7000::/36 Valid RIR databaseARIN 635 100% 69

AS-SET

AS54643's PeeringDB record names no 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 51 are in fix.csv.

  • ROA: none6
  • Route object: none3
  • Route object: RIR13
  • Route object: not announced29
ChangePrefix or setDetailFull-table peers
ROA: none69.90.223.0/24No ROA covers it. Add a ROA for AS54643, maxLength 24.673 of 673
Route object: RIR69.90.223.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none69.90.243.0/24No ROA covers it. Add a ROA for AS54643, maxLength 24.673 of 673
Route object: RIR69.90.243.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none70.33.247.0/24No ROA covers it. Add a ROA for AS54643, maxLength 24.673 of 673
Route object: RIR70.33.247.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none107.6.27.0/24No ROA covers it. Add a ROA for AS54643, maxLength 24.673 of 673
Route object: RIR107.6.27.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none64.69.79.0/24No ROA covers it. Add a ROA for AS54643, maxLength 24.2 of 673
Route object: RIR64.69.79.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none107.6.20.0/23No ROA covers it. Add a ROA for AS54643, maxLength 23.2 of 673
Route object: RIR107.6.20.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: none23.111.72.0/23No route object for it. A route object for 23.111.64.0/20 with origin AS54643 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54643 in the RIR database for the space.673 of 673
Route object: none23.111.74.0/23No route object for it. A route object for 23.111.64.0/20 with origin AS54643 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54643 in the RIR database for the space.673 of 673
Route object: none67.231.16.0/21No route object for it. A route object for 67.231.16.0/20 with origin AS54643 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54643 in the RIR database for the space.673 of 673
Route object: RIR64.34.70.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR64.34.72.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR67.231.24.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR67.231.28.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR67.231.30.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR104.36.148.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR104.36.150.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

23.111.64.0/20RADBNo ROA
64.34.111.0/24RADBValid
64.69.64.0/24RADBNo ROA
65.39.182.0/24RADBNo ROA
65.39.240.0/24RADBNo ROA
65.39.242.0/24RADBNo ROA
66.85.28.0/22RADBNo ROA
66.199.174.0/24RADBNo ROA
66.199.185.0/24RADBNo ROA
67.231.16.0/20RADBValid
69.90.62.0/24RADBNo ROA
69.90.63.0/24RADBNo ROA
69.90.148.0/23RADBNo ROA
69.172.198.0/23RADBNo ROA
69.172.218.0/24RADBNo ROA
69.172.248.0/23RADBNo ROA
70.33.214.0/23RADBNo ROA
76.74.186.0/23RADBNo ROA
76.74.229.0/24RADBNo ROA
76.74.231.0/24RADBNo ROA
76.74.246.0/23RADBNo ROA
104.36.148.0/22RADBValid
104.193.172.0/22RADBNo ROA
107.6.26.0/24RADBNo ROA
162.248.27.0/24RADBNo ROA
162.248.28.0/24RADBNo ROA
216.187.70.0/24RADBNo ROA
216.187.92.0/23RADBNo ROA
216.187.99.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.