bgpreport

Network · data from 2026-11-12

AS9772 JBBANK-AS-KR-KR - Jeonbuk Bank

Registry name: JBBANK-AS-KR-KR - Jeonbuk Bank, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9772, 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.
119.206.23.128/26 No ROA None 14 2%low visibility 13
211.230.122.192/26 No ROA None 14 2%low visibility 13
218.151.31.0/24 No ROA Other IRR onlyRADB 673 100% 66

AS-SET

AS9772 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 34 are in fix.csv.

  • ROA: none3
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced28
ChangePrefix or setDetailFull-table peers
ROA: none119.206.23.128/26No ROA covers it. Add a ROA for AS9772, maxLength 26.14 of 673
Route object: none119.206.23.128/26No route object for it. Add a route object with origin AS9772 in the RIR database for the space.14 of 673
ROA: none211.230.122.192/26No ROA covers it. Add a ROA for AS9772, maxLength 26.14 of 673
Route object: none211.230.122.192/26No route object for it. Add a route object with origin AS9772 in the RIR database for the space.14 of 673
ROA: none218.151.31.0/24No ROA covers it. Add a ROA for AS9772, maxLength 24.673 of 673
Route object: RIR218.151.31.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

1.232.171.0/24RADBNo ROA
1.240.9.0/24RADBNo ROA
1.240.10.0/24RADBNo ROA
1.240.11.0/24RADBNo ROA
1.240.12.0/24RADBNo ROA
58.29.0.0/24RADBNo ROA
58.29.16.0/21RADBNo ROA
58.29.23.0/24RADBNo ROA
111.218.32.0/22RADBNo ROA
111.218.36.0/23RADBNo ROA
111.218.38.0/24RADBNo ROA
124.2.64.128/25RADBNo ROA
124.138.2.0/23RADBNo ROA
124.138.4.0/22RADBNo ROA
124.138.5.128/25RADBNo ROA
124.138.6.128/25RADBNo ROA
124.138.8.0/24RADBNo ROA
124.138.8.128/25RADBNo ROA
124.138.9.0/24RADBNo ROA
124.138.10.0/24RADBNo ROA
124.138.11.0/24RADBNo ROA
124.138.12.0/22RADBNo ROA
124.138.15.64/28RADBNo ROA
125.241.120.0/21RADBNo ROA
125.241.128.0/21RADBNo ROA
210.122.0.0/20RADBNo ROA
210.126.224.0/20RADBNo ROA
211.173.22.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.