bgpreport

Network · data from 2026-11-12

AS151061 WPSDL-AS-AP - Winning Partner Software Development Limited

Registry name: WPSDL-AS-AP - Winning Partner Software Development Limited, HK · not in PeeringDB

3IPv4 routes 33.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
2Route objects not announced registered with origin AS151061, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS151061, 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.

38.47.60.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
38.150.73.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
103.126.40.0/23 Valid RIR databaseAPNIC 673 100% 67
2001:df2:37c0::/48 Valid RIR databaseAPNIC 635 100% 69

AS-SET

AS151061 isn't in PeeringDB, where networks name their 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 6 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none38.47.60.0/24No ROA covers it. Add a ROA for AS151061, maxLength 24.672 of 673
Route object: RIR38.47.60.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none38.150.73.0/24No ROA covers it. Add a ROA for AS151061, maxLength 24.672 of 673
Route object: RIR38.150.73.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

103.126.40.0/24APNICValid
103.126.41.0/24APNICValid

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.