bgpreport

Network · data from 2026-11-12

AS152920 ZHAOCHENGLIN-AS-AP - Zhao Chenglin

Registry name: ZHAOCHENGLIN-AS-AP - Zhao Chenglin, CN · not in PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 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
0Low visibility seen by under 10% of full-table peers
38Route objects not announced registered with origin AS152920, seen from no peer

Announced routes

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

144.225.186.0/24 Valid RIR databaseARIN, RADB 673 100% 67
87.76.221.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
87.76.222.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
151.247.148.0/23 Valid RIR databaseRADB, RIPE 672 100% 67
154.91.158.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
154.91.159.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
156.237.104.0/23 Valid RIR databaseAFRINIC, RADB 672 100% 67
2a0f:2706::/32 Valid RIR databaseRIPE 636 100% 69
2406:840:fcd0::/48 Valid RIR databaseAPNIC, RADB 634 100% 69
2406:840:fe96::/48 Valid RIR databaseAPNIC 634 100% 69

AS-SET

AS152920 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 38 are in fix.csv.

  • Route object: not announced38

Route objects not announced

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

154.208.140.0/22AFRINICNo ROA
154.208.144.0/20AFRINICNo ROA
154.208.160.0/21AFRINICNo ROA
154.208.172.0/23AFRINICNo ROA
154.208.174.0/24AFRINICInvalid: origin
156.231.3.0/24RADBValid
156.231.7.0/24RADBValid
2406:840:fcd0::/44APNICValid
2406:840:fcd0::/45APNICValid
2406:840:fcd0::/46APNICValid
2406:840:fcd0::/47APNICValid
2406:840:fcd1::/48APNICValid
2406:840:fcd2::/47APNICValid
2406:840:fcd2::/48APNICValid
2406:840:fcd3::/48APNICValid
2406:840:fcd4::/46APNICValid
2406:840:fcd4::/47APNICValid
2406:840:fcd4::/48APNICValid
2406:840:fcd5::/48APNICValid
2406:840:fcd6::/47APNICValid
2406:840:fcd6::/48APNICValid
2406:840:fcd7::/48APNICValid
2406:840:fcd8::/45APNICValid
2406:840:fcd8::/46APNICValid
2406:840:fcd8::/47APNICValid
2406:840:fcd8::/48APNICValid
2406:840:fcd9::/48APNICValid
2406:840:fcda::/47APNICValid
2406:840:fcda::/48APNICValid
2406:840:fcdb::/48APNICValid
2406:840:fcdc::/46APNICValid
2406:840:fcdc::/47APNICValid
2406:840:fcdc::/48APNICValid
2406:840:fcdd::/48APNICValid
2406:840:fcde::/47APNICValid
2406:840:fcde::/48APNICValid
2406:840:fcdf::/48APNICValid
2a0f:cf40::/40RIPEValid

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.