bgpreport

Network · data from 2026-11-12

AS141180 HUAWEI INTERNATIONAL

Registry name: HIPL-AS-AP - HUAWEI INTERNATIONAL PTE. LTD., SG · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS141180, 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.
87.119.9.0/24 No ROA Other IRR onlyRADB 672 100% 66
87.119.3.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
87.119.4.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
87.119.10.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
87.119.11.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
87.119.17.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
87.119.18.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
87.119.19.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
87.119.32.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
87.119.33.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
87.119.7.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
87.119.13.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
87.119.34.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
87.119.8.0/24 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2

AS-SET

AS141180'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 18 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none87.119.9.0/24No ROA covers it. Add a ROA for AS141180, maxLength 24.672 of 673
Route object: RIR87.119.9.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

14.137.152.0/22APNIC, RADBNo ROA
14.137.154.0/24APNIC, RADBInvalid: origin
87.119.0.0/24APNIC, RADBNo ROA
87.119.1.0/24APNIC, RADBNo ROA
87.119.2.0/24APNIC, RADBValid
87.119.5.0/24APNIC, RADBValid
87.119.6.0/24APNIC, RADBValid
87.119.14.0/24APNIC, RADBValid
87.119.15.0/24APNIC, RADBValid
87.119.16.0/24APNIC, RADBValid
115.108.58.0/24APNICValid
115.108.62.0/24APNICValid
119.13.160.0/24APNIC, RADBValid
167.179.255.0/24APNIC, RADBValid
180.87.59.0/24APNICValid
2a02:e0:3138::/48RIPEValid

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.