bgpreport

Network · data from 2026-11-12

AS19174 China Unicom (Americas) Operations Ltd

Registry name: AS19174 - China Unicom (Americas) Operations Ltd, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS19174, 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.
199.102.95.0/24 No ROA Other origin onlycovered by 199.102.92.0/22 673 100% 67
207.254.177.0/24 No ROA Nonecovered by 207.254.176.0/20 673 100% 67
207.254.190.0/24 No ROA Other origin onlycovered by 207.254.176.0/20 673 100% 67
207.254.189.0/24 No ROA Other origin onlycovered by 207.254.176.0/20 670 100% 67
207.254.180.0/24 No ROA Other origin onlycovered by 207.254.176.0/20 71 11% 33
207.254.186.0/24 No ROA Other IRR onlyRADB 673 100% 67
199.102.92.0/22 No ROA RIR databaseARIN 673 100% 67
207.254.176.0/20 No ROA RIR databaseARIN, RADB 673 100% 67

AS-SET

AS19174'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 19 are in fix.csv.

  • ROA: none8
  • Route object: none5
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none199.102.95.0/24No ROA covers it. Add a ROA for AS19174, maxLength 24.673 of 673
Route object: none199.102.95.0/24Route objects for it name AS10099. A route object for 199.102.92.0/22 with origin AS19174 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19174 in the RIR database for the space.673 of 673
ROA: none207.254.177.0/24No ROA covers it. Add a ROA for AS19174, maxLength 24.673 of 673
Route object: none207.254.177.0/24No route object for it. A route object for 207.254.176.0/20 with origin AS19174 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19174 in the RIR database for the space.673 of 673
ROA: none207.254.190.0/24No ROA covers it. Add a ROA for AS19174, maxLength 24.673 of 673
Route object: none207.254.190.0/24Route objects for it name AS10099. A route object for 207.254.176.0/20 with origin AS19174 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19174 in the RIR database for the space.673 of 673
ROA: none207.254.189.0/24No ROA covers it. Add a ROA for AS19174, maxLength 24.670 of 673
Route object: none207.254.189.0/24Route objects for it name AS10099. A route object for 207.254.176.0/20 with origin AS19174 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19174 in the RIR database for the space.670 of 673
ROA: none207.254.180.0/24No ROA covers it. Add a ROA for AS19174, maxLength 24.71 of 673
Route object: none207.254.180.0/24Route objects for it name AS10099. A route object for 207.254.176.0/20 with origin AS19174 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19174 in the RIR database for the space.71 of 673
ROA: none207.254.186.0/24No ROA covers it. Add a ROA for AS19174, maxLength 24.673 of 673
Route object: RIR207.254.186.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none199.102.92.0/22No ROA covers it. Add a ROA for AS19174, maxLength 22.673 of 673
ROA: none207.254.176.0/20No ROA covers it. Add a ROA for AS19174, maxLength 20.673 of 673

Route objects not announced

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

199.102.92.0/24ARINNo ROA
207.254.185.0/24RADBNo ROA
207.254.187.0/24RADBNo ROA
2604:bf80::/32ARINNo ROA
2604:bf80:c000::/34ARINNo 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.