bgpreport

Network · data from 2026-11-12

AS9863 EDUCAR-AS-KR-KR - Hana Insurance Co., Ltd.

Registry name: EDUCAR-AS-KR-KR - Hana Insurance Co., Ltd., KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9863, 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.121.183.0/25 No ROA None 16 2%low visibility 13
61.36.51.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS9863 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: none1
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none222.121.183.0/25No ROA covers it. Add a ROA for AS9863, maxLength 25.16 of 673
Route object: none222.121.183.0/25No route object for it. Add a route object with origin AS9863 in the RIR database for the space.16 of 673
ROA: none61.36.51.0/24No ROA covers it. Add a ROA for AS9863, maxLength 24.673 of 673
Route object: RIR61.36.51.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 AS9863 whose prefix no peer sees AS9863 announce. Many are kept on purpose (backup routes, space announced only in some places).

61.37.252.0/24NTTCOM, RADBNo ROA
211.115.112.0/20RADBNo 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.