bgpreport

Network · data from 2026-11-12

AS139791 WOPAI-AS-AP - Langfang Wopai Communications Co Ltd

Registry name: WOPAI-AS-AP - Langfang Wopai Communications Co Ltd, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS139791, 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:3600:e000::/40 Invalid: origin None 3 0%low visibility 3
213.214.110.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2a0a:d681:e000::/40 Valid Nonecovered by 2a0a:d681::/32 635 100% 68
2406:840:feca::/48 Valid RIR databaseAPNIC 634 100% 69

AS-SET

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

  • ROA: origin2
  • Route object: none3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin2a06:3600:e000::/40ROAs covering it name AS60781, not AS139791. If AS139791 should announce it, add a ROA for AS139791.3 of 636
Route object: none2a06:3600:e000::/40No route object for it. Add a route object with origin AS139791 in the RIR database for the space.3 of 636
ROA: origin213.214.110.0/24ROAs covering it name AS834, not AS139791. If AS139791 should announce it, add a ROA for AS139791.2 of 673
Route object: none213.214.110.0/24Route objects for it name AS834. Add a route object with origin AS139791 in the RIR database for the space.2 of 673
Route object: none2a0a:d681:e000::/40No route object for it. A route object for 2a0a:d681::/32 with origin AS139791 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139791 in the RIR database for the space.635 of 636

Route objects not announced

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

2a0a:d681::/32RIPEValid
2a0a:d681::/35RIPEValid

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.