bgpreport

Network · data from 2026-11-12

AS45058 XMGBNET - Golden-Bridge Netcom communication Co.,LTD.

Registry name: XMGBNET - Golden-Bridge Netcom communication Co.,LTD., CN · not in PeeringDB

28IPv4 routes 35.7% RPKI valid · 7.1% with a route object
0IPv6 routes
7RPKI invalid 7 origin · 0 maxLength
11No ROA 26 with no route object for this origin
28Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS45058, seen from no peer

Announced routes

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

114.113.64.0/22 Invalid: origin None 4 1%low visibility 4
114.113.112.0/21 Invalid: origin None 4 1%low visibility 4
114.113.112.0/22 Invalid: origin None 4 1%low visibility 4
114.113.116.0/22 Invalid: origin None 4 1%low visibility 4
114.113.118.0/24 Invalid: origin None 4 1%low visibility 4
114.113.119.0/24 Invalid: origin None 4 1%low visibility 4
114.113.124.0/22 Invalid: origin None 4 1%low visibility 4
117.79.160.0/21 No ROA None 44 7%low visibility 30
218.240.8.0/24 No ROA None 44 7%low visibility 30
218.240.32.0/19 No ROA Other origin only 44 7%low visibility 30
218.240.56.0/21 No ROA None 44 7%low visibility 30
218.240.166.0/24 No ROA None 44 7%low visibility 30
218.240.168.0/22 No ROA None 44 7%low visibility 30
218.240.169.0/24 No ROA None 44 7%low visibility 30
218.240.170.0/24 No ROA None 44 7%low visibility 30
218.240.171.0/24 No ROA None 44 7%low visibility 30
218.240.32.0/21 No ROA Other IRR onlyNTTCOM, RADB 44 7%low visibility 30
218.240.48.0/21 No ROA Other IRR onlyNTTCOM, RADB 44 7%low visibility 30
118.186.7.0/24 Valid None 44 7%low visibility 30
118.186.88.0/21 Valid None 44 7%low visibility 30
118.186.128.0/19 Valid None 44 7%low visibility 30
118.186.208.0/22 Valid None 44 7%low visibility 30
118.186.212.0/22 Valid None 44 7%low visibility 30
118.187.64.0/19 Valid None 44 7%low visibility 30
118.187.254.0/23 Valid None 44 7%low visibility 30
218.240.180.0/24 Valid None 44 7%low visibility 30
218.240.181.0/24 Valid None 44 7%low visibility 30
218.240.183.0/24 Valid None 44 7%low visibility 30

AS-SET

AS45058 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 50 are in fix.csv.

  • ROA: origin7
  • ROA: none11
  • Route object: none26
  • Route object: RIR2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin114.113.64.0/22An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS45058 should announce it, add a ROA for AS45058.4 of 673
Route object: none114.113.64.0/22No route object for it. Add a route object with origin AS45058 in the RIR database for the space.4 of 673
ROA: origin114.113.112.0/21An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS45058 should announce it, add a ROA for AS45058.4 of 673
Route object: none114.113.112.0/21No route object for it. Add a route object with origin AS45058 in the RIR database for the space.4 of 673
ROA: origin114.113.112.0/22An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS45058 should announce it, add a ROA for AS45058.4 of 673
Route object: none114.113.112.0/22No route object for it. Add a route object with origin AS45058 in the RIR database for the space.4 of 673
ROA: origin114.113.116.0/22An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS45058 should announce it, add a ROA for AS45058.4 of 673
Route object: none114.113.116.0/22No route object for it. Add a route object with origin AS45058 in the RIR database for the space.4 of 673
ROA: origin114.113.118.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS45058 should announce it, add a ROA for AS45058.4 of 673
Route object: none114.113.118.0/24No route object for it. Add a route object with origin AS45058 in the RIR database for the space.4 of 673
ROA: origin114.113.119.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS45058 should announce it, add a ROA for AS45058.4 of 673
Route object: none114.113.119.0/24No route object for it. Add a route object with origin AS45058 in the RIR database for the space.4 of 673
ROA: origin114.113.124.0/22An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS45058 should announce it, add a ROA for AS45058.4 of 673
Route object: none114.113.124.0/22No route object for it. Add a route object with origin AS45058 in the RIR database for the space.4 of 673
ROA: none117.79.160.0/21No ROA covers it. Add a ROA for AS45058, maxLength 21.44 of 673
Route object: none117.79.160.0/21No route object for it. Add a route object with origin AS45058 in the RIR database for the space.44 of 673
ROA: none218.240.8.0/24No ROA covers it. Add a ROA for AS45058, maxLength 24.44 of 673
Route object: none218.240.8.0/24No route object for it. Add a route object with origin AS45058 in the RIR database for the space.44 of 673
ROA: none218.240.32.0/19No ROA covers it. Add a ROA for AS45058, maxLength 19.44 of 673
Route object: none218.240.32.0/19Route objects for it name AS4808, AS4847. Add a route object with origin AS45058 in the RIR database for the space.44 of 673
ROA: none218.240.56.0/21No ROA covers it. Add a ROA for AS45058, maxLength 21.44 of 673
Route object: none218.240.56.0/21No route object for it. Add a route object with origin AS45058 in the RIR database for the space.44 of 673
ROA: none218.240.166.0/24No ROA covers it. Add a ROA for AS45058, maxLength 24.44 of 673
Route object: none218.240.166.0/24No route object for it. Add a route object with origin AS45058 in the RIR database for the space.44 of 673
ROA: none218.240.168.0/22No ROA covers it. Add a ROA for AS45058, maxLength 22.44 of 673
Route object: none218.240.168.0/22No route object for it. Add a route object with origin AS45058 in the RIR database for the space.44 of 673
ROA: none218.240.169.0/24No ROA covers it. Add a ROA for AS45058, maxLength 24.44 of 673
Route object: none218.240.169.0/24No route object for it. Add a route object with origin AS45058 in the RIR database for the space.44 of 673
ROA: none218.240.170.0/24No ROA covers it. Add a ROA for AS45058, maxLength 24.44 of 673
Route object: none218.240.170.0/24No route object for it. Add a route object with origin AS45058 in the RIR database for the space.44 of 673
ROA: none218.240.171.0/24No ROA covers it. Add a ROA for AS45058, maxLength 24.44 of 673
Route object: none218.240.171.0/24No route object for it. Add a route object with origin AS45058 in the RIR database for the space.44 of 673
ROA: none218.240.32.0/21No ROA covers it. Add a ROA for AS45058, maxLength 21.44 of 673
Route object: RIR218.240.32.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.44 of 673
ROA: none218.240.48.0/21No ROA covers it. Add a ROA for AS45058, maxLength 21.44 of 673
Route object: RIR218.240.48.0/21Route object only in NTTCOM, RADB. Add it in the RIR database for the space.44 of 673
Route object: none118.186.7.0/24No route object for it. Add a route object with origin AS45058 in the RIR database for the space.44 of 673
Route object: none118.186.88.0/21No route object for it. Add a route object with origin AS45058 in the RIR database for the space.44 of 673
Route object: none118.186.128.0/19No route object for it. Add a route object with origin AS45058 in the RIR database for the space.44 of 673
Route object: none118.186.208.0/22No route object for it. Add a route object with origin AS45058 in the RIR database for the space.44 of 673
Route object: none118.186.212.0/22No route object for it. Add a route object with origin AS45058 in the RIR database for the space.44 of 673
Route object: none118.187.64.0/19No route object for it. Add a route object with origin AS45058 in the RIR database for the space.44 of 673
Route object: none118.187.254.0/23No route object for it. Add a route object with origin AS45058 in the RIR database for the space.44 of 673
Route object: none218.240.180.0/24No route object for it. Add a route object with origin AS45058 in the RIR database for the space.44 of 673
Route object: none218.240.181.0/24No route object for it. Add a route object with origin AS45058 in the RIR database for the space.44 of 673
Route object: none218.240.183.0/24No route object for it. Add a route object with origin AS45058 in the RIR database for the space.44 of 673

Route objects not announced

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

218.240.0.0/21NTTCOM, RADBNo ROA
218.240.16.0/21NTTCOM, RADBNo ROA
218.240.24.0/21NTTCOM, RADBNo ROA
218.240.40.0/21NTTCOM, RADBNo 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.