bgpreport

Network · data from 2026-11-12

AS38419 AS0999-AS-KR-KR - Kyobo Lifeplanet Life Insurance Company

Registry name: AS0999-AS-KR-KR - Kyobo Lifeplanet Life Insurance Company, KR · not in PeeringDB

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

Announced routes

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

218.52.186.80/28 No ROA None 3 0%low visibility 3
218.52.186.96/27 No ROA None 3 0%low visibility 3

AS-SET

AS38419 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 6 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none218.52.186.80/28No ROA covers it. Add a ROA for AS38419, maxLength 28.3 of 673
Route object: none218.52.186.80/28No route object for it. Add a route object with origin AS38419 in the RIR database for the space.3 of 673
ROA: none218.52.186.96/27No ROA covers it. Add a ROA for AS38419, maxLength 27.3 of 673
Route object: none218.52.186.96/27No route object for it. Add a route object with origin AS38419 in the RIR database for the space.3 of 673

Route objects not announced

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

61.33.31.128/25RADBNo ROA
121.140.162.0/25RADBNo 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.