bgpreport

Network · data from 2026-11-12

AS10062 BHA-AS-KR-KR - Branksome Hall Asia

Registry name: BHA-AS-KR-KR - Branksome Hall Asia, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10062, 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.
222.122.101.0/24 No ROA None 671 100% 67
121.124.138.208/29 No ROA None 9 1%low visibility 9
1.249.108.0/24 No ROA Other IRR onlyRADB 671 100% 67
58.229.99.0/24 No ROA Other IRR onlyRADB 671 100% 67
58.238.84.0/24 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

AS10062 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 32 are in fix.csv.

  • ROA: none5
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced22
ChangePrefix or setDetailFull-table peers
ROA: none222.122.101.0/24No ROA covers it. Add a ROA for AS10062, maxLength 24.671 of 673
Route object: none222.122.101.0/24No route object for it. Add a route object with origin AS10062 in the RIR database for the space.671 of 673
ROA: none121.124.138.208/29No ROA covers it. Add a ROA for AS10062, maxLength 29.9 of 673
Route object: none121.124.138.208/29No route object for it. Add a route object with origin AS10062 in the RIR database for the space.9 of 673
ROA: none1.249.108.0/24No ROA covers it. Add a ROA for AS10062, maxLength 24.671 of 673
Route object: RIR1.249.108.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none58.229.99.0/24No ROA covers it. Add a ROA for AS10062, maxLength 24.671 of 673
Route object: RIR58.229.99.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none58.238.84.0/24No ROA covers it. Add a ROA for AS10062, maxLength 24.671 of 673
Route object: RIR58.238.84.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

58.102.0.0/15RADBNo ROA
58.102.62.0/23RADBNo ROA
58.103.32.0/24RADBNo ROA
106.249.50.0/24RADBNo ROA
118.220.211.0/24NTTCOM, RADBNo ROA
118.220.212.0/22RADBNo ROA
118.220.212.0/24NTTCOMNo ROA
118.220.213.0/24NTTCOMNo ROA
118.220.214.0/24NTTCOMNo ROA
118.220.215.0/24NTTCOMNo ROA
118.220.216.0/23RADBNo ROA
118.220.216.0/24NTTCOMNo ROA
118.220.217.0/24NTTCOMNo ROA
211.47.201.0/24RADBNo ROA
211.47.215.0/24RADBNo ROA
211.47.216.0/22NTTCOM, RADBNo ROA
211.47.220.0/24RADBNo ROA
211.242.9.0/24RADBNo ROA
211.242.10.0/23RADBNo ROA
211.242.12.0/22RADBNo ROA
211.242.16.0/23RADBNo ROA
211.242.18.0/24RADBNo 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.