bgpreport

Network · data from 2026-11-12

AS38583 ASE IT Networks

Registry name: ASEIT-AS-AP - Andrew Sjoquist Enterprises Pty Ltd, AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38583, 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.
125.214.88.0/21 Valid RIR databaseAPNIC 671 100% 67
43.243.236.0/24 Valid RIR databaseAPNIC 670 100% 67
43.243.237.0/24 Valid RIR databaseAPNIC 670 100% 67
103.24.240.0/23 Valid RIR databaseAPNIC 670 100% 67
103.24.240.0/24 Valid RIR databaseAPNIC 670 100% 67
103.24.241.0/24 Valid RIR databaseAPNIC 670 100% 67
103.39.60.0/22 Valid RIR databaseAPNIC 670 100% 67
103.224.208.0/24 Valid RIR databaseAPNIC 670 100% 67
103.224.209.0/24 Valid RIR databaseAPNIC 670 100% 67
103.224.211.0/24 Valid RIR databaseAPNIC 670 100% 67
113.29.244.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
113.29.246.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
175.184.193.0/24 Valid RIR databaseAPNIC 670 100% 67
175.184.195.0/24 Valid RIR databaseAPNIC 670 100% 67
175.184.196.0/24 Valid RIR databaseAPNIC 670 100% 67
175.184.197.0/24 Valid RIR databaseAPNIC 670 100% 67
175.184.199.0/24 Valid RIR databaseAPNIC 670 100% 67
175.184.216.0/24 Valid RIR databaseAPNIC 670 100% 67
175.184.217.0/24 Valid RIR databaseAPNIC 670 100% 67
175.184.221.0/24 Valid RIR databaseAPNIC 670 100% 67
175.184.222.0/24 Valid RIR databaseAPNIC 670 100% 67
175.184.223.0/24 Valid RIR databaseAPNIC 670 100% 67
103.249.127.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 669 99% 67
113.29.246.0/23 Valid RIR databaseAPNIC, NTTCOM, RADB 167 25% 51

AS-SET

AS38583'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 21 are in fix.csv.

  • Route object: not announced21

Route objects not announced

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

103.129.156.0/22NTTCOM, RADBNo ROA
113.29.244.0/22APNIC, NTTCOM, RADBValid
113.29.244.0/24APNICValid
113.29.245.0/24APNICValid
113.29.247.0/24APNIC, RADBValid
125.214.88.0/22APNICValid
125.214.88.0/23APNICValid
125.214.88.0/24APNICValid
125.214.89.0/24APNICValid
125.214.90.0/23APNICValid
125.214.90.0/24APNICValid
125.214.91.0/24APNICValid
125.214.92.0/22APNICValid
125.214.92.0/23APNICValid
125.214.92.0/24APNICValid
125.214.93.0/24APNICValid
125.214.94.0/23APNICValid
125.214.94.0/24APNICValid
125.214.95.0/24APNICValid
125.254.1.0/24RADBNo ROA
203.20.68.0/23NTTCOMNo 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.