bgpreport

Network · data from 2026-11-12

AS131874 KDBC-AS-KR-KR - KDB CAPITAL CORPORATION

Registry name: KDBC-AS-KR-KR - KDB CAPITAL CORPORATION, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS131874, 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.
121.67.84.128/26 No ROA None 3 0%low visibility 3
121.67.84.192/26 No ROA None 3 0%low visibility 3
211.178.8.0/27 No ROA None 3 0%low visibility 3
211.178.8.32/27 No ROA None 3 0%low visibility 3
180.64.199.0/24 No ROA Other IRR onlyRADB 673 100% 67
211.168.42.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS131874 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 12 are in fix.csv.

  • ROA: none6
  • Route object: none4
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none121.67.84.128/26No ROA covers it. Add a ROA for AS131874, maxLength 26.3 of 673
Route object: none121.67.84.128/26No route object for it. Add a route object with origin AS131874 in the RIR database for the space.3 of 673
ROA: none121.67.84.192/26No ROA covers it. Add a ROA for AS131874, maxLength 26.3 of 673
Route object: none121.67.84.192/26No route object for it. Add a route object with origin AS131874 in the RIR database for the space.3 of 673
ROA: none211.178.8.0/27No ROA covers it. Add a ROA for AS131874, maxLength 27.3 of 673
Route object: none211.178.8.0/27No route object for it. Add a route object with origin AS131874 in the RIR database for the space.3 of 673
ROA: none211.178.8.32/27No ROA covers it. Add a ROA for AS131874, maxLength 27.3 of 673
Route object: none211.178.8.32/27No route object for it. Add a route object with origin AS131874 in the RIR database for the space.3 of 673
ROA: none180.64.199.0/24No ROA covers it. Add a ROA for AS131874, maxLength 24.673 of 673
Route object: RIR180.64.199.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.168.42.0/24No ROA covers it. Add a ROA for AS131874, maxLength 24.673 of 673
Route object: RIR211.168.42.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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