bgpreport

Network · data from 2026-11-12

AS58627 Oneasia Network Limited

Registry name: ONEASIA-NET-AS - OneAsia Network Limited, HK · PeeringDB

20IPv4 routes 90.0% RPKI valid · 95.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
16Route objects not announced registered with origin AS58627, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS58627, 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.
154.18.156.0/22 No ROA None 172 26% 55
2404:3500::/32 No ROA Other IRR onlyRADB 635 100% 68
154.18.157.0/24 No ROA Other IRR onlyRADB 346 51% 64
103.9.244.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 67
103.9.245.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 67
103.9.246.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 67
103.9.247.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 67
43.242.239.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
43.242.236.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 69
43.242.237.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 69
43.242.238.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 69
103.1.32.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
103.1.32.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
103.1.33.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
103.1.34.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
103.1.35.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
103.9.244.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 69
45.119.0.0/24 Valid RIR databaseAPNIC 670 100% 67
45.119.1.0/24 Valid RIR databaseAPNIC 670 100% 67
45.119.2.0/24 Valid RIR databaseAPNIC 670 100% 67
45.119.3.0/24 Valid RIR databaseAPNIC 670 100% 67

AS-SET

AS58627'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 22 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none154.18.156.0/22No ROA covers it. Add a ROA for AS58627, maxLength 22.172 of 673
Route object: none154.18.156.0/22No route object for it. Add a route object with origin AS58627 in the RIR database for the space.172 of 673
ROA: none2404:3500::/32No ROA covers it. Add a ROA for AS58627, maxLength 32.635 of 636
Route object: RIR2404:3500::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none154.18.157.0/24No ROA covers it. Add a ROA for AS58627, maxLength 24.346 of 673
Route object: RIR154.18.157.0/24Route object only in RADB. Add it in the RIR database for the space.346 of 673

Route objects not announced

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

0.242.236.0/24NTTCOMNo ROA
43.242.236.0/22APNIC, NTTCOM, RADBValid
103.137.150.0/24APNICNo ROA
103.150.104.0/24APNICNo ROA
110.92.76.0/24APNICValid
110.92.77.0/24APNICValid
110.92.78.0/24APNICValid
110.92.79.0/24APNICValid
154.18.156.0/24RADBNo ROA
154.18.158.0/24RADBNo ROA
154.18.159.0/24RADBNo ROA
203.80.0.0/22APNICNo ROA
210.79.130.0/23APNICValid
210.79.130.0/24APNICValid
210.79.131.0/24APNICValid
2401:5460::/32APNICValid

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.