bgpreport

Network · data from 2026-11-12

AS211512 SCG-EU Nebula Global Limited

Registry name: SCG-EU Nebula Global Limited, HK · not in PeeringDB

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

Announced routes

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

207.57.80.0/20 Invalid: origin Other IRR onlyNTTCOM 32 5%low visibility 21
207.57.96.0/21 Invalid: origin Other IRR onlyNTTCOM 32 5%low visibility 21
154.38.74.0/24 No ROA Other IRR onlyRADB 671 100% 67
154.38.75.0/24 No ROA Other IRR onlyRADB 671 100% 67
154.38.100.0/24 No ROA Other IRR onlyRADB 671 100% 67
154.38.101.0/24 No ROA Other IRR onlyRADB 671 100% 67
154.38.102.0/24 No ROA Other IRR onlyRADB 671 100% 67
154.38.103.0/24 No ROA Other IRR onlyRADB 671 100% 67
154.38.244.0/24 No ROA Other IRR onlyRADB 671 100% 67
154.38.245.0/24 No ROA Other IRR onlyRADB 671 100% 67
154.38.246.0/24 No ROA Other IRR onlyRADB 671 100% 67
154.38.247.0/24 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

AS211512 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 24 are in fix.csv.

  • ROA: origin2
  • ROA: none10
  • Route object: RIR12
ChangePrefix or setDetailFull-table peers
ROA: origin207.57.80.0/20ROAs covering it name AS2914, not AS211512. If AS211512 should announce it, add a ROA for AS211512.32 of 673
Route object: RIR207.57.80.0/20Route object only in NTTCOM. Add it in the RIR database for the space.32 of 673
ROA: origin207.57.96.0/21ROAs covering it name AS2914, not AS211512. If AS211512 should announce it, add a ROA for AS211512.32 of 673
Route object: RIR207.57.96.0/21Route object only in NTTCOM. Add it in the RIR database for the space.32 of 673
ROA: none154.38.74.0/24No ROA covers it. Add a ROA for AS211512, maxLength 24.671 of 673
Route object: RIR154.38.74.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none154.38.75.0/24No ROA covers it. Add a ROA for AS211512, maxLength 24.671 of 673
Route object: RIR154.38.75.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none154.38.100.0/24No ROA covers it. Add a ROA for AS211512, maxLength 24.671 of 673
Route object: RIR154.38.100.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none154.38.101.0/24No ROA covers it. Add a ROA for AS211512, maxLength 24.671 of 673
Route object: RIR154.38.101.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none154.38.102.0/24No ROA covers it. Add a ROA for AS211512, maxLength 24.671 of 673
Route object: RIR154.38.102.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none154.38.103.0/24No ROA covers it. Add a ROA for AS211512, maxLength 24.671 of 673
Route object: RIR154.38.103.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none154.38.244.0/24No ROA covers it. Add a ROA for AS211512, maxLength 24.671 of 673
Route object: RIR154.38.244.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none154.38.245.0/24No ROA covers it. Add a ROA for AS211512, maxLength 24.671 of 673
Route object: RIR154.38.245.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none154.38.246.0/24No ROA covers it. Add a ROA for AS211512, maxLength 24.671 of 673
Route object: RIR154.38.246.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none154.38.247.0/24No ROA covers it. Add a ROA for AS211512, maxLength 24.671 of 673
Route object: RIR154.38.247.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 AS211512 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.