bgpreport

Network · data from 2026-11-12

AS214040 RUNNAN WEN

Registry name: WEN-NET RUNNAN WEN, CN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS214040, 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.
2a06:1281:8000::/36 Invalid: origin Other origin only 1 0%low visibility 1
2a0f:6280:8000::/36 Valid RIR databaseRIPE 634 100% 68
2a0f:6280:9000::/36 Valid RIR databaseRIPE 634 100% 68
2a0f:6280:a000::/36 Valid RIR databaseRIPE 634 100% 68
2a0f:6282:1000::/36 Valid RIR databaseRIPE 634 100% 68
2a0f:6280:d000::/36 Valid RIR databaseRIPE 632 99% 69
2a0f:6280:e000::/36 Valid RIR databaseRIPE 632 99% 69
2a0f:6282:a000::/36 Valid RIR databaseRIPE 632 99% 69
2a0f:6282:e000::/36 Valid RIR databaseRIPE 632 99% 69
2a0f:6283:2000::/36 Valid RIR databaseRIPE 632 99% 69
2a0f:6283:8000::/36 Valid RIR databaseRIPE 632 99% 69

AS-SET

AS214040'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 3 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin2a06:1281:8000::/36ROAs covering it name AS213864, not AS214040. If AS214040 should announce it, add a ROA for AS214040.1 of 636
Route object: none2a06:1281:8000::/36Route objects for it name AS213864. Add a route object with origin AS214040 in the RIR database for the space.1 of 636

Route objects not announced

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

2a0f:7803:f7a0::/44RADBNo ROA

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.