bgpreport

Network · data from 2026-11-12

AS201674 WENZHANGYU Wen ZhangYu

Registry name: WENZHANGYU Wen ZhangYu, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS201674, 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.
178.236.38.0/23 Invalid: origin RIR databaseRIPE 292 43% 61
95.82.8.0/24 Valid Nonecovered by 95.82.8.0/23 669 99% 66
95.82.9.0/24 Valid Nonecovered by 95.82.8.0/23 669 99% 66
2a06:9801:20::/48 Valid Other IRR onlyRADB 634 100% 70
95.82.8.0/23 Valid RIR databaseRIPE 670 100% 66

AS-SET

AS201674 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 4 are in fix.csv.

  • ROA: origin1
  • Route object: none2
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: origin178.236.38.0/23An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS201674 should announce it, add a ROA for AS201674.292 of 673
Route object: none95.82.8.0/24No route object for it. A route object for 95.82.8.0/23 with origin AS201674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201674 in the RIR database for the space.669 of 673
Route object: none95.82.9.0/24No route object for it. A route object for 95.82.8.0/23 with origin AS201674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201674 in the RIR database for the space.669 of 673
Route object: RIR2a06:9801:20::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

Every route object with origin AS201674 is announced.

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.