bgpreport

Network · data from 2026-11-12

AS38087 BUSANBANK2-AS-KR-KR - BUSANBANK

Registry name: BUSANBANK2-AS-KR-KR - BUSANBANK, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38087, 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.
211.53.102.0/24 No ROA None 673 100% 67
121.175.28.0/24 No ROA Other IRR onlyRADB 673 100% 67
210.183.119.192/26 No ROA Other IRR onlyRADB 14 2%low visibility 13

AS-SET

AS38087 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 11 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none211.53.102.0/24No ROA covers it. Add a ROA for AS38087, maxLength 24.673 of 673
Route object: none211.53.102.0/24No route object for it. Add a route object with origin AS38087 in the RIR database for the space.673 of 673
ROA: none121.175.28.0/24No ROA covers it. Add a ROA for AS38087, maxLength 24.673 of 673
Route object: RIR121.175.28.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none210.183.119.192/26No ROA covers it. Add a ROA for AS38087, maxLength 26.14 of 673
Route object: RIR210.183.119.192/26Route object only in RADB. Add it in the RIR database for the space.14 of 673

Route objects not announced

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

61.254.128.0/24NTTCOMNo ROA
219.252.192.0/24NTTCOMNo ROA
219.252.193.0/24NTTCOMNo ROA
219.252.197.0/24NTTCOMNo ROA
219.252.200.0/24NTTCOMNo 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.