bgpreport

Network · data from 2026-11-12

AS150141 Wang Jiacheng

Registry name: W1N0DL-AS-AP - Wang Jiacheng, CN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS150141, 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.
2406:840:fef5::/48 Valid RIR databaseAPNIC 635 100% 69
2602:faa8:708::/48 Valid RIR databaseARIN 635 100% 69
2602:faa8:709::/48 Valid RIR databaseARIN 635 100% 67
2406:840:e280::/44 Valid RIR databaseAPNIC, RADB 634 100% 69
2406:840:e280::/48 Valid RIR databaseAPNIC 634 100% 69
2406:840:e281::/48 Valid RIR databaseAPNIC 634 100% 69
2406:840:e282::/48 Valid RIR databaseAPNIC 634 100% 69
2406:840:e283::/48 Valid RIR databaseAPNIC 634 100% 69
2406:840:e284::/48 Valid RIR databaseAPNIC 634 100% 69
2406:840:e285::/48 Valid RIR databaseAPNIC 634 100% 69
2406:840:e286::/48 Valid RIR databaseAPNIC 634 100% 69
2406:840:e287::/48 Valid RIR databaseAPNIC 634 100% 69
2406:840:e288::/48 Valid RIR databaseAPNIC 634 100% 69
2406:840:e289::/48 Valid RIR databaseAPNIC 634 100% 69
2406:840:e28a::/48 Valid RIR databaseAPNIC 634 100% 69
2406:840:e28b::/48 Valid RIR databaseAPNIC 634 100% 69
2406:840:e28c::/48 Valid RIR databaseAPNIC 634 100% 69
2406:840:e28d::/48 Valid RIR databaseAPNIC 634 100% 69
2406:840:e28e::/48 Valid RIR databaseAPNIC 634 100% 69
2406:840:e28f::/48 Valid RIR databaseAPNIC 634 100% 69
2602:faa8:70f::/48 Valid RIR databaseARIN 634 100% 68
2602:faa8:702::/48 Valid RIR databaseARIN 1 0%low visibility 1

AS-SET

AS150141'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 27 are in fix.csv.

  • Route object: not announced27

Route objects not announced

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

2406:840:e280::/45APNICValid
2406:840:e280::/46APNICValid
2406:840:e280::/47APNICValid
2406:840:e282::/47APNICValid
2406:840:e284::/46APNICValid
2406:840:e284::/47APNICValid
2406:840:e286::/47APNICValid
2406:840:e288::/45APNICValid
2406:840:e288::/46APNICValid
2406:840:e288::/47APNICValid
2406:840:e28a::/47APNICValid
2406:840:e28c::/46APNICValid
2406:840:e28c::/47APNICValid
2406:840:e28e::/47APNICValid
2602:faa8:700::/44ARINValid
2602:faa8:700::/48ARINValid
2602:faa8:701::/48ARINValid
2602:faa8:703::/48ARINValid
2602:faa8:704::/48ARINValid
2602:faa8:705::/48ARINValid
2602:faa8:706::/48ARINValid
2602:faa8:707::/48ARINValid
2602:faa8:70a::/48ARINValid
2602:faa8:70b::/48ARINValid
2602:faa8:70c::/48ARINValid
2602:faa8:70d::/48ARINValid
2602:faa8:70e::/48ARINValid

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.