bgpreport

Network · data from 2026-11-12

AS137263 NETEASE

Registry name: NETEASE-AS-AP - NETEASE HONG KONG LIMITED, HK · PeeringDB

43IPv4 routes 95.3% 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
2No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
17Route objects not announced registered with origin AS137263, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS137263, 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.236.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
154.18.237.0/24 No ROA Other IRR onlyNTTCOM, RADB 670 100% 67
113.21.92.0/24 Valid Other IRR onlyRADB 670 100% 67
150.116.81.0/24 Valid Other IRR onlyRADB 670 100% 67
154.81.10.0/24 Valid Other IRR onlyRADB 669 99% 67
156.224.81.0/24 Valid Other IRR onlyRADB 669 99% 67
156.245.2.0/24 Valid Other IRR onlyRADB 669 99% 67
156.253.4.0/24 Valid Other IRR onlyRADB 669 99% 67
156.236.16.0/24 Valid Other IRR onlyRADB 668 99% 67
103.131.191.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
103.135.241.0/24 Valid RIR databaseAPNIC 672 100% 67
103.135.242.0/23 Valid RIR databaseAPNIC, RADB 672 100% 67
160.236.52.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
160.236.53.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
205.210.164.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
45.195.16.0/21 Valid RIR databaseAFRINIC, RADB 671 100% 67
103.126.92.0/22 Valid RIR databaseAPNIC, RADB 670 100% 67
103.126.92.0/23 Valid RIR databaseAPNIC, RADB 670 100% 67
103.126.94.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
103.126.95.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
103.129.252.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
103.129.252.0/23 Valid RIR databaseAPNIC, RADB 670 100% 67
103.129.252.0/24 Valid RIR databaseAPNIC 670 100% 67
103.135.240.0/22 Valid RIR databaseAPNIC, RADB 670 100% 67
103.135.240.0/23 Valid RIR databaseAPNIC, RADB 670 100% 67
103.209.128.0/24 Valid RIR databaseAPNIC 670 100% 67
185.122.207.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
193.233.194.0/24 Valid RIR databaseRIPE 670 100% 67
154.86.4.0/24 Valid RIR databaseAFRINIC, RADB 669 99% 67
154.86.5.0/24 Valid RIR databaseAFRINIC, RADB 669 99% 67
154.203.247.0/24 Valid RIR databaseAFRINIC, RADB 669 99% 67
156.224.82.0/24 Valid RIR databaseAFRINIC, RADB 669 99% 67
156.224.83.0/24 Valid RIR databaseAFRINIC, RADB 669 99% 67
156.225.180.0/24 Valid RIR databaseAFRINIC, RADB 669 99% 67
156.250.2.0/24 Valid RIR databaseAFRINIC, RADB 669 99% 67
210.79.60.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
45.195.16.0/24 Valid RIR databaseAFRINIC, RADB 668 99% 67
45.195.19.0/24 Valid RIR databaseAFRINIC, RADB 668 99% 67
45.195.20.0/24 Valid RIR databaseAFRINIC, RADB 668 99% 67
45.195.23.0/24 Valid RIR databaseAFRINIC, RADB 668 99% 67
45.195.24.0/24 Valid RIR databaseAFRINIC, RADB 668 99% 67
45.195.138.0/24 Valid RIR databaseAFRINIC, RADB 668 99% 67
103.129.254.0/23 Valid RIR databaseAPNIC, RADB 667 99% 67
2403:9d40::/32 Valid RIR databaseAPNIC, RADB 636 100% 67

AS-SET

AS137263'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 28 are in fix.csv.

  • ROA: none2
  • Route object: RIR9
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: none154.18.236.0/24No ROA covers it. Add a ROA for AS137263, maxLength 24.671 of 673
Route object: RIR154.18.236.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none154.18.237.0/24No ROA covers it. Add a ROA for AS137263, maxLength 24.670 of 673
Route object: RIR154.18.237.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR113.21.92.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR150.116.81.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR154.81.10.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR156.224.81.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR156.245.2.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR156.253.4.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR156.236.16.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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

45.192.22.0/24AFRINICInvalid: origin
45.192.23.0/24AFRINICInvalid: origin
45.192.24.0/24AFRINICInvalid: origin
45.195.17.0/24AFRINIC, RADBValid
45.195.18.0/24AFRINIC, RADBValid
45.195.21.0/24AFRINIC, RADBValid
45.195.22.0/24AFRINIC, RADBValid
45.196.16.0/21AFRINICNo ROA
103.126.94.0/23APNIC, RADBValid
109.107.168.0/23RADBNo ROA
154.86.4.0/23RADBValid
156.224.82.0/23RADBValid
160.236.52.0/23APNIC, RADBValid
193.233.194.0/23RIPEValid
193.233.195.0/24RIPEValid
2404:8c0::/32RADBNo ROA
2404:8740::/32RADBNo 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.