bgpreport

Network · data from 2026-11-12

AS18118 CITIC Networks Management

Registry name: CITICNET-CN - CITIC Networks Management Co.,Ltd., CN · PeeringDB

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

Announced routes

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

120.47.0.0/19 Valid Nonecovered by 120.47.0.0/16 672 100% 67
120.47.32.0/19 Valid Nonecovered by 120.47.0.0/16 672 100% 67
120.47.64.0/19 Valid Nonecovered by 120.47.0.0/16 672 100% 67
120.47.96.0/19 Valid Nonecovered by 120.47.0.0/16 672 100% 67
120.47.128.0/19 Valid Nonecovered by 120.47.0.0/16 672 100% 67
120.47.160.0/19 Valid Nonecovered by 120.47.0.0/16 672 100% 67
120.47.223.0/24 Valid Nonecovered by 120.47.0.0/16 672 100% 67
120.47.224.0/24 Valid Nonecovered by 120.47.0.0/16 672 100% 67
120.47.225.0/24 Valid Nonecovered by 120.47.0.0/16 672 100% 67
120.47.226.0/24 Valid Nonecovered by 120.47.0.0/16 672 100% 67
120.47.227.0/24 Valid Nonecovered by 120.47.0.0/16 672 100% 67
120.47.228.0/24 Valid Nonecovered by 120.47.0.0/16 672 100% 67
219.72.200.0/22 Valid Nonecovered by 219.72.0.0/16 672 100% 67
219.72.240.0/23 Valid Nonecovered by 219.72.0.0/16 672 100% 67
219.72.250.0/24 Valid Nonecovered by 219.72.0.0/16 672 100% 67
219.72.32.0/20 Valid Nonecovered by 219.72.0.0/16 671 100% 67
219.72.68.0/24 Valid Nonecovered by 219.72.0.0/16 671 100% 67
219.72.128.0/24 Valid Nonecovered by 219.72.0.0/16 671 100% 67
219.72.252.0/24 Valid Nonecovered by 219.72.0.0/16 671 100% 67
219.72.69.0/24 Valid Nonecovered by 219.72.0.0/16 57 8%low visibility 33
219.72.153.0/24 Valid Nonecovered by 219.72.152.0/22 45 7%low visibility 30
219.72.156.0/22 Valid Nonecovered by 219.72.0.0/16 45 7%low visibility 30
219.72.156.0/24 Valid Nonecovered by 219.72.0.0/16 45 7%low visibility 30
219.72.155.0/24 Valid Nonecovered by 219.72.152.0/22 44 7%low visibility 30
219.72.241.0/24 Valid Nonecovered by 219.72.0.0/16 44 7%low visibility 30
120.45.0.0/16 Valid Other IRR onlyRADB 672 100% 67
120.45.16.0/20 Valid Other IRR onlyRADB 672 100% 67
120.45.48.0/20 Valid Other IRR onlyRADB 672 100% 67
120.45.80.0/20 Valid Other IRR onlyRADB 672 100% 67
120.45.112.0/20 Valid Other IRR onlyRADB 672 100% 67
120.45.129.0/24 Valid Other IRR onlyRADB 672 100% 67
120.45.136.0/24 Valid Other IRR onlyRADB 672 100% 67
120.45.140.0/24 Valid Other IRR onlyRADB 672 100% 67
120.45.255.0/24 Valid Other IRR onlyRADB 672 100% 67
120.47.0.0/16 Valid Other IRR onlyRADB 672 100% 67
219.72.152.0/22 Valid Other IRR onlyNTTCOM, RADB 45 7%low visibility 30
219.72.0.0/16 Valid RIR databaseAPNIC 672 100% 67

AS-SET

AS18118'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 39 are in fix.csv.

  • Route object: none25
  • Route object: RIR11
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none120.47.0.0/19No route object for it. A route object for 120.47.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.672 of 673
Route object: none120.47.32.0/19No route object for it. A route object for 120.47.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.672 of 673
Route object: none120.47.64.0/19No route object for it. A route object for 120.47.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.672 of 673
Route object: none120.47.96.0/19No route object for it. A route object for 120.47.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.672 of 673
Route object: none120.47.128.0/19No route object for it. A route object for 120.47.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.672 of 673
Route object: none120.47.160.0/19No route object for it. A route object for 120.47.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.672 of 673
Route object: none120.47.223.0/24No route object for it. A route object for 120.47.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.672 of 673
Route object: none120.47.224.0/24No route object for it. A route object for 120.47.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.672 of 673
Route object: none120.47.225.0/24No route object for it. A route object for 120.47.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.672 of 673
Route object: none120.47.226.0/24No route object for it. A route object for 120.47.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.672 of 673
Route object: none120.47.227.0/24No route object for it. A route object for 120.47.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.672 of 673
Route object: none120.47.228.0/24No route object for it. A route object for 120.47.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.672 of 673
Route object: none219.72.200.0/22No route object for it. A route object for 219.72.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.672 of 673
Route object: none219.72.240.0/23No route object for it. A route object for 219.72.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.672 of 673
Route object: none219.72.250.0/24No route object for it. A route object for 219.72.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.672 of 673
Route object: none219.72.32.0/20No route object for it. A route object for 219.72.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.671 of 673
Route object: none219.72.68.0/24No route object for it. A route object for 219.72.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.671 of 673
Route object: none219.72.128.0/24No route object for it. A route object for 219.72.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.671 of 673
Route object: none219.72.252.0/24No route object for it. A route object for 219.72.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.671 of 673
Route object: none219.72.69.0/24No route object for it. A route object for 219.72.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.57 of 673
Route object: none219.72.153.0/24No route object for it. A route object for 219.72.152.0/22 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.45 of 673
Route object: none219.72.156.0/22No route object for it. A route object for 219.72.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.45 of 673
Route object: none219.72.156.0/24No route object for it. A route object for 219.72.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.45 of 673
Route object: none219.72.155.0/24No route object for it. A route object for 219.72.152.0/22 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.44 of 673
Route object: none219.72.241.0/24No route object for it. A route object for 219.72.0.0/16 with origin AS18118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18118 in the RIR database for the space.44 of 673
Route object: RIR120.45.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR120.45.16.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR120.45.48.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR120.45.80.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR120.45.112.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR120.45.129.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR120.45.136.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR120.45.140.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR120.45.255.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR120.47.0.0/16Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR219.72.152.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.45 of 673

Route objects not announced

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

219.72.60.0/24APNICInvalid: maxLength
219.72.167.0/24APNICInvalid: maxLength
219.72.240.0/24APNICInvalid: maxLength

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.