bgpreport

Network · data from 2026-11-12

AS45083 BGTELECOM - China UNICOM, Beijing Branch

Registry name: BGTELECOM - China UNICOM, Beijing Branch, CN · not in PeeringDB

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

Announced routes

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

1.45.0.0/16 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.0.0/17 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.16.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.20.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.24.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.28.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.32.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.36.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.40.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.44.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.48.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.52.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.56.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.60.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.64.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.68.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.72.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.76.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.80.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.84.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.88.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.92.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.96.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.100.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.104.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.108.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.112.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.116.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.120.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.124.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.128.0/17 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.128.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.132.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.136.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.140.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.144.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.148.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.152.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.156.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.160.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.164.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.168.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.172.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.176.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.180.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.184.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.188.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.192.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.196.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.200.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.204.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
1.45.208.0/22 Valid Other IRR onlyNTTCOM, RADB 673 100% 67

AS-SET

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

  • Route object: RIR52
ChangePrefix or setDetailFull-table peers
Route object: RIR1.45.0.0/16Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.0.0/17Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.16.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.20.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.24.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.28.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.32.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.36.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.40.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.44.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.48.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.52.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.56.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.60.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.64.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.68.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.72.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.76.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.80.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.84.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.88.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.92.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.96.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.100.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.104.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.108.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.112.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.116.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.120.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.124.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.128.0/17Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.128.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.132.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.136.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.140.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.144.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.148.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.152.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.156.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.160.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.164.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.168.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.172.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.176.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.180.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.184.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.188.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.192.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.196.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.200.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.204.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR1.45.208.0/22Route 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 AS45083 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.