bgpreport

Network · data from 2026-11-12

AS56012 LGNET-China - LGNET China

Registry name: LGNET-China - LGNET China, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56012, 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.
203.148.64.0/24 No ROA Other origin onlycovered by 203.148.64.0/20 673 100% 67
203.148.65.0/24 No ROA Other origin onlycovered by 203.148.64.0/20 673 100% 67
203.148.74.0/24 No ROA Other origin onlycovered by 203.148.64.0/20 672 100% 67
203.148.64.0/20 No ROA Other IRR onlyRADB 673 100% 67
203.148.75.0/24 No ROA Other IRR onlyRADB 671 100% 67
203.148.76.0/24 No ROA Other IRR onlyRADB 671 100% 67
203.148.77.0/24 No ROA Other IRR onlyRADB 671 100% 67
203.148.78.0/24 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

AS56012 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 16 are in fix.csv.

  • ROA: none8
  • Route object: none3
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none203.148.64.0/24No ROA covers it. Add a ROA for AS56012, maxLength 24.673 of 673
Route object: none203.148.64.0/24Route objects for it name AS10224. A route object for 203.148.64.0/20 with origin AS56012 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56012 in the RIR database for the space.673 of 673
ROA: none203.148.65.0/24No ROA covers it. Add a ROA for AS56012, maxLength 24.673 of 673
Route object: none203.148.65.0/24Route objects for it name AS10224. A route object for 203.148.64.0/20 with origin AS56012 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56012 in the RIR database for the space.673 of 673
ROA: none203.148.74.0/24No ROA covers it. Add a ROA for AS56012, maxLength 24.672 of 673
Route object: none203.148.74.0/24Route objects for it name AS10224, AS17895. A route object for 203.148.64.0/20 with origin AS56012 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56012 in the RIR database for the space.672 of 673
ROA: none203.148.64.0/20No ROA covers it. Add a ROA for AS56012, maxLength 20.673 of 673
Route object: RIR203.148.64.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.148.75.0/24No ROA covers it. Add a ROA for AS56012, maxLength 24.671 of 673
Route object: RIR203.148.75.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none203.148.76.0/24No ROA covers it. Add a ROA for AS56012, maxLength 24.671 of 673
Route object: RIR203.148.76.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none203.148.77.0/24No ROA covers it. Add a ROA for AS56012, maxLength 24.671 of 673
Route object: RIR203.148.77.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none203.148.78.0/24No ROA covers it. Add a ROA for AS56012, maxLength 24.671 of 673
Route object: RIR203.148.78.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS56012 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.