bgpreport

Network · data from 2026-11-12

AS132813 AISI-AS-AP - HK AISI CLOUD COMPUTING LIMITED

Registry name: AISI-AS-AP - HK AISI CLOUD COMPUTING LIMITED, HK · not in PeeringDB

32IPv4 routes 62.5% RPKI valid · 37.5% with a route object
0IPv6 routes
12RPKI invalid 12 origin · 0 maxLength
0No ROA 20 with no route object for this origin
21Low visibility seen by under 10% of full-table peers
13Route objects not announced registered with origin AS132813, seen from no peer

Announced routes

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

103.84.88.0/24 Invalid: origin None 2 0%low visibility 2
103.84.89.0/24 Invalid: origin None 2 0%low visibility 2
103.84.90.0/24 Invalid: origin None 2 0%low visibility 2
103.84.91.0/24 Invalid: origin None 2 0%low visibility 2
103.214.140.0/24 Invalid: origin None 2 0%low visibility 2
103.214.141.0/24 Invalid: origin None 2 0%low visibility 2
103.214.142.0/24 Invalid: origin None 2 0%low visibility 2
103.214.143.0/24 Invalid: origin None 2 0%low visibility 2
216.250.104.0/24 Invalid: origin None 2 0%low visibility 2
216.250.105.0/24 Invalid: origin None 2 0%low visibility 2
216.250.106.0/24 Invalid: origin None 2 0%low visibility 2
216.250.107.0/24 Invalid: origin None 2 0%low visibility 2
45.195.52.0/24 Valid Nonecovered by 45.195.52.0/22 670 100% 67
45.195.53.0/24 Valid Nonecovered by 45.195.52.0/22 670 100% 67
45.195.54.0/24 Valid Nonecovered by 45.195.52.0/22 670 100% 67
45.195.55.0/24 Valid Nonecovered by 45.195.52.0/22 670 100% 67
154.211.20.0/24 Valid Nonecovered by 154.211.20.0/22 2 0%low visibility 2
154.211.21.0/24 Valid Nonecovered by 154.211.20.0/22 2 0%low visibility 2
154.211.22.0/24 Valid Nonecovered by 154.211.20.0/22 2 0%low visibility 2
154.211.23.0/24 Valid Nonecovered by 154.211.20.0/22 2 0%low visibility 2
45.204.56.0/22 Valid Other IRR onlyRADB 671 100% 67
156.253.8.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
156.253.9.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
103.74.172.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
116.89.248.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
116.89.249.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
116.89.250.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
116.89.251.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
154.205.8.0/22 Valid RIR databaseAFRINIC, RADB 671 100% 67
103.74.172.0/24 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2
103.74.173.0/24 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2
103.74.174.0/24 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2

AS-SET

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

  • ROA: origin12
  • Route object: none20
  • Route object: RIR3
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: origin103.84.88.0/24ROAs covering it name AS136222, not AS132813. If AS132813 should announce it, add a ROA for AS132813.2 of 673
Route object: none103.84.88.0/24No route object for it. Add a route object with origin AS132813 in the RIR database for the space.2 of 673
ROA: origin103.84.89.0/24ROAs covering it name AS136222, not AS132813. If AS132813 should announce it, add a ROA for AS132813.2 of 673
Route object: none103.84.89.0/24No route object for it. Add a route object with origin AS132813 in the RIR database for the space.2 of 673
ROA: origin103.84.90.0/24ROAs covering it name AS136222, not AS132813. If AS132813 should announce it, add a ROA for AS132813.2 of 673
Route object: none103.84.90.0/24No route object for it. Add a route object with origin AS132813 in the RIR database for the space.2 of 673
ROA: origin103.84.91.0/24ROAs covering it name AS136222, not AS132813. If AS132813 should announce it, add a ROA for AS132813.2 of 673
Route object: none103.84.91.0/24No route object for it. Add a route object with origin AS132813 in the RIR database for the space.2 of 673
ROA: origin103.214.140.0/24ROAs covering it name AS135331, not AS132813. If AS132813 should announce it, add a ROA for AS132813.2 of 673
Route object: none103.214.140.0/24No route object for it. Add a route object with origin AS132813 in the RIR database for the space.2 of 673
ROA: origin103.214.141.0/24ROAs covering it name AS135331, not AS132813. If AS132813 should announce it, add a ROA for AS132813.2 of 673
Route object: none103.214.141.0/24No route object for it. Add a route object with origin AS132813 in the RIR database for the space.2 of 673
ROA: origin103.214.142.0/24ROAs covering it name AS135331, not AS132813. If AS132813 should announce it, add a ROA for AS132813.2 of 673
Route object: none103.214.142.0/24No route object for it. Add a route object with origin AS132813 in the RIR database for the space.2 of 673
ROA: origin103.214.143.0/24ROAs covering it name AS135331, not AS132813. If AS132813 should announce it, add a ROA for AS132813.2 of 673
Route object: none103.214.143.0/24No route object for it. Add a route object with origin AS132813 in the RIR database for the space.2 of 673
ROA: origin216.250.104.0/24ROAs covering it name AS135331, not AS132813. If AS132813 should announce it, add a ROA for AS132813.2 of 673
Route object: none216.250.104.0/24No route object for it. Add a route object with origin AS132813 in the RIR database for the space.2 of 673
ROA: origin216.250.105.0/24ROAs covering it name AS135331, not AS132813. If AS132813 should announce it, add a ROA for AS132813.2 of 673
Route object: none216.250.105.0/24No route object for it. Add a route object with origin AS132813 in the RIR database for the space.2 of 673
ROA: origin216.250.106.0/24ROAs covering it name AS135331, not AS132813. If AS132813 should announce it, add a ROA for AS132813.2 of 673
Route object: none216.250.106.0/24No route object for it. Add a route object with origin AS132813 in the RIR database for the space.2 of 673
ROA: origin216.250.107.0/24ROAs covering it name AS135331, not AS132813. If AS132813 should announce it, add a ROA for AS132813.2 of 673
Route object: none216.250.107.0/24No route object for it. Add a route object with origin AS132813 in the RIR database for the space.2 of 673
Route object: none45.195.52.0/24No route object for it. A route object for 45.195.52.0/22 with origin AS132813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132813 in the RIR database for the space.670 of 673
Route object: none45.195.53.0/24No route object for it. A route object for 45.195.52.0/22 with origin AS132813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132813 in the RIR database for the space.670 of 673
Route object: none45.195.54.0/24No route object for it. A route object for 45.195.52.0/22 with origin AS132813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132813 in the RIR database for the space.670 of 673
Route object: none45.195.55.0/24No route object for it. A route object for 45.195.52.0/22 with origin AS132813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132813 in the RIR database for the space.670 of 673
Route object: none154.211.20.0/24No route object for it. A route object for 154.211.20.0/22 with origin AS132813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132813 in the RIR database for the space.2 of 673
Route object: none154.211.21.0/24No route object for it. A route object for 154.211.20.0/22 with origin AS132813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132813 in the RIR database for the space.2 of 673
Route object: none154.211.22.0/24No route object for it. A route object for 154.211.20.0/22 with origin AS132813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132813 in the RIR database for the space.2 of 673
Route object: none154.211.23.0/24No route object for it. A route object for 154.211.20.0/22 with origin AS132813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132813 in the RIR database for the space.2 of 673
Route object: RIR45.204.56.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR156.253.8.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR156.253.9.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

45.195.52.0/22AFRINIC, NTTCOM, RADBValid
45.195.56.0/23AFRINIC, NTTCOM, RADBValid
45.204.8.0/21AFRINIC, RADBValid
103.89.137.0/24APNIC, RADBValid
116.89.248.0/22APNIC, RADBValid
154.91.32.0/22AFRINIC, RADBValid
154.91.35.0/24AFRINIC, RADBValid
154.205.6.0/23AFRINIC, RADBValid
154.211.20.0/22AFRINIC, RADBValid
156.226.16.0/21AFRINIC, RADBValid
156.253.8.0/21AFRINIC, NTTCOM, RADBValid
156.254.126.0/23AFRINIC, RADBValid
156.254.127.0/24RADBValid

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.