bgpreport

Network · data from 2026-11-12

AS134542 UNICOM-GUIAN - China Unicom IP network

Registry name: UNICOM-GUIAN - China Unicom IP network, CN · not in PeeringDB

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

Announced routes

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

59.80.0.0/17 Valid None 673 100% 67
59.80.0.0/19 Valid None 673 100% 67
59.80.32.0/19 Valid None 673 100% 67
59.80.64.0/19 Valid None 673 100% 67
59.80.96.0/19 Valid None 673 100% 67
2408:877f:31::/48 Valid Nonecovered by 2408:877f::/32 629 99% 67
2407:c080:1800::/37 Valid Other origin only 176 28% 41
103.161.220.0/23 Valid Other origin only 134 20% 44
122.9.160.0/20 Valid Other origin only 126 19% 45
122.9.128.0/19 Valid Other origin only 125 19% 45
116.63.128.0/18 Valid Other origin only 124 18% 44
139.9.144.0/20 Valid Other origin only 120 18% 44
139.9.240.0/21 Valid Other origin only 113 17% 44
139.9.248.0/22 Valid Other origin only 112 17% 44
139.9.224.0/20 Valid Other origin only 109 16% 44
140.210.192.0/19 Valid Other origin only 109 16% 43
140.210.224.0/20 Valid Other origin only 109 16% 43
43.254.100.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
43.254.101.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
43.254.102.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
43.254.103.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
2408:877f::/32 Valid RIR databaseAPNIC 629 99% 67

AS-SET

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

  • Route object: none17
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
Route object: none59.80.0.0/17No route object for it. Add a route object with origin AS134542 in the RIR database for the space.673 of 673
Route object: none59.80.0.0/19No route object for it. Add a route object with origin AS134542 in the RIR database for the space.673 of 673
Route object: none59.80.32.0/19No route object for it. Add a route object with origin AS134542 in the RIR database for the space.673 of 673
Route object: none59.80.64.0/19No route object for it. Add a route object with origin AS134542 in the RIR database for the space.673 of 673
Route object: none59.80.96.0/19No route object for it. Add a route object with origin AS134542 in the RIR database for the space.673 of 673
Route object: none2408:877f:31::/48No route object for it. A route object for 2408:877f::/32 with origin AS134542 covers it (filters allowing more-specifics accept it). Add a route object with origin AS134542 in the RIR database for the space.629 of 636
Route object: none2407:c080:1800::/37Route objects for it name AS58519, AS138407. Add a route object with origin AS134542 in the RIR database for the space.176 of 636
Route object: none103.161.220.0/23Route objects for it name AS58519. Add a route object with origin AS134542 in the RIR database for the space.134 of 673
Route object: none122.9.160.0/20Route objects for it name AS58519. Add a route object with origin AS134542 in the RIR database for the space.126 of 673
Route object: none122.9.128.0/19Route objects for it name AS58519. Add a route object with origin AS134542 in the RIR database for the space.125 of 673
Route object: none116.63.128.0/18Route objects for it name AS58519. Add a route object with origin AS134542 in the RIR database for the space.124 of 673
Route object: none139.9.144.0/20Route objects for it name AS58519. Add a route object with origin AS134542 in the RIR database for the space.120 of 673
Route object: none139.9.240.0/21Route objects for it name AS58519. Add a route object with origin AS134542 in the RIR database for the space.113 of 673
Route object: none139.9.248.0/22Route objects for it name AS58519. Add a route object with origin AS134542 in the RIR database for the space.112 of 673
Route object: none139.9.224.0/20Route objects for it name AS58519. Add a route object with origin AS134542 in the RIR database for the space.109 of 673
Route object: none140.210.192.0/19Route objects for it name AS58519. Add a route object with origin AS134542 in the RIR database for the space.109 of 673
Route object: none140.210.224.0/20Route objects for it name AS58519. Add a route object with origin AS134542 in the RIR database for the space.109 of 673
Route object: RIR43.254.100.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR43.254.101.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR43.254.102.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR43.254.103.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS134542 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.