bgpreport

Network · data from 2026-11-12

AS45990 HIRANET-AS-KR-KR - Health Insurance Review Assessment Service

Registry name: HIRANET-AS-KR-KR - Health Insurance Review Assessment Service, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45990, 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.
103.206.75.128/25 No ROA Nonecovered by 103.206.75.0/24 3 0%low visibility 3
125.244.124.64/26 No ROA None 3 0%low visibility 3
125.244.125.0/26 No ROA None 3 0%low visibility 3
125.244.125.128/26 No ROA None 3 0%low visibility 3
103.206.74.0/24 No ROA Other IRR onlyRADB 673 100% 67
103.206.75.0/24 No ROA Other IRR onlyRADB 673 100% 67
211.42.100.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS45990 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 22 are in fix.csv.

  • ROA: none7
  • Route object: none4
  • Route object: RIR3
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none103.206.75.128/25No ROA covers it. Add a ROA for AS45990, maxLength 25.3 of 673
Route object: none103.206.75.128/25No route object for it. A route object for 103.206.75.0/24 with origin AS45990 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45990 in the RIR database for the space.3 of 673
ROA: none125.244.124.64/26No ROA covers it. Add a ROA for AS45990, maxLength 26.3 of 673
Route object: none125.244.124.64/26No route object for it. Add a route object with origin AS45990 in the RIR database for the space.3 of 673
ROA: none125.244.125.0/26No ROA covers it. Add a ROA for AS45990, maxLength 26.3 of 673
Route object: none125.244.125.0/26No route object for it. Add a route object with origin AS45990 in the RIR database for the space.3 of 673
ROA: none125.244.125.128/26No ROA covers it. Add a ROA for AS45990, maxLength 26.3 of 673
Route object: none125.244.125.128/26No route object for it. Add a route object with origin AS45990 in the RIR database for the space.3 of 673
ROA: none103.206.74.0/24No ROA covers it. Add a ROA for AS45990, maxLength 24.673 of 673
Route object: RIR103.206.74.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none103.206.75.0/24No ROA covers it. Add a ROA for AS45990, maxLength 24.673 of 673
Route object: RIR103.206.75.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none211.42.100.0/24No ROA covers it. Add a ROA for AS45990, maxLength 24.673 of 673
Route object: RIR211.42.100.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 AS45990 whose prefix no peer sees AS45990 announce. Many are kept on purpose (backup routes, space announced only in some places).

1.242.60.0/26RADBNo ROA
58.120.82.0/26RADBNo ROA
58.227.216.0/24NTTCOM, RADBNo ROA
58.227.217.0/24NTTCOM, RADBNo ROA
116.123.74.0/24RADBNo ROA
121.135.156.0/24RADBNo ROA
175.116.110.192/26RADBNo ROA
210.205.156.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.