bgpreport

Network · data from 2026-11-12

AS150150 AISANIE DATA SERVICES LIMITED

Registry name: AISANIE1-AS-AP - AISANIE DATA SERVICES LIMITED, HK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS150150, 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.
206.238.226.0/24 No ROA Other IRR onlyRADB 671 100% 67
38.67.211.0/24 No ROA Other IRR onlyRADB 670 100% 67
38.110.231.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
206.238.154.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
156.230.62.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
103.8.215.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
103.147.172.0/24 Valid RIR databaseAPNIC 671 100% 67
154.89.0.0/24 Valid RIR databaseAFRINIC, RADB 670 100% 67
2402:3960:1000::/48 Valid RIR databaseAPNIC 636 100% 68
38.110.230.0/24 Valid RIR databaseARIN 2 0%low visibility 2

AS-SET

AS150150'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 19 are in fix.csv.

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none206.238.226.0/24No ROA covers it. Add a ROA for AS150150, maxLength 24.671 of 673
Route object: RIR206.238.226.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.67.211.0/24No ROA covers it. Add a ROA for AS150150, maxLength 24.670 of 673
Route object: RIR38.67.211.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.110.231.0/24No ROA covers it. Add a ROA for AS150150, maxLength 24.2 of 673
Route object: RIR38.110.231.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none206.238.154.0/24No ROA covers it. Add a ROA for AS150150, maxLength 24.2 of 673
Route object: RIR206.238.154.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 AS150150 whose prefix no peer sees AS150150 announce. Many are kept on purpose (backup routes, space announced only in some places).

38.83.16.0/24RADBNo ROA
38.123.160.0/24RADBNo ROA
38.123.161.0/24RADBNo ROA
206.238.224.0/24RADBNo ROA
206.238.229.0/24RADBNo ROA
2402:3960::/32APNICValid
2402:3960:2000::/48APNICValid
2402:3960:3000::/48APNICValid
2402:3960:4000::/48APNICValid
2402:3960:5000::/48APNICValid
2402:3960:6000::/48APNICValid

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.