bgpreport

Network · data from 2026-11-12

AS139148 CHINAUNIONPAY

Registry name: CHINAUNIONPAY - China UnionPay Co., Ltd, CN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS139148, 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.
115.172.36.0/22 Valid None 673 100% 67
115.172.46.0/23 Valid None 673 100% 67
2405:78c0:6e0e::/48 Valid Nonecovered by 2405:78c0:6e00::/44 636 100% 68
2405:78c0:6e10::/44 Valid Nonecovered by 2405:78c0::/32 619 97% 67
2405:78c0:6e1e::/48 Valid Nonecovered by 2405:78c0::/32 619 97% 67
103.145.42.0/24 Valid Other IRR onlyRADB 673 100% 67
103.145.43.0/24 Valid Other IRR onlyRADB 673 100% 67
115.172.32.0/22 Valid Other IRR onlyRADB 673 100% 67
2405:78c0:6e00::/44 Valid Other IRR onlyRADB 636 100% 68

AS-SET

AS139148'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 11 are in fix.csv.

  • Route object: none5
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none115.172.36.0/22No route object for it. Add a route object with origin AS139148 in the RIR database for the space.673 of 673
Route object: none115.172.46.0/23No route object for it. Add a route object with origin AS139148 in the RIR database for the space.673 of 673
Route object: none2405:78c0:6e0e::/48No route object for it. A route object for 2405:78c0:6e00::/44 with origin AS139148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139148 in the RIR database for the space.636 of 636
Route object: none2405:78c0:6e10::/44No route object for it. A route object for 2405:78c0::/32 with origin AS139148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139148 in the RIR database for the space.619 of 636
Route object: none2405:78c0:6e1e::/48No route object for it. A route object for 2405:78c0::/32 with origin AS139148 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139148 in the RIR database for the space.619 of 636
Route object: RIR103.145.42.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.145.43.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR115.172.32.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2405:78c0:6e00::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

103.145.42.0/23RADBValid
2405:78c0::/32RADBValid

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.