bgpreport

Network · data from 2026-11-12

AS23990 MIGUM-AS-KR-KR - MigumCableNetwork

Registry name: MIGUM-AS-KR-KR - MigumCableNetwork, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS23990, 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.
114.52.243.0/24 No ROA Other origin only 2 0%low visibility 2
58.102.226.0/24 No ROA Other IRR onlyNTTCOM, RADB 2 0%low visibility 2
61.104.42.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
61.104.43.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
61.104.45.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
114.52.239.0/24 No ROA Other IRR onlyNTTCOM 2 0%low visibility 2
114.52.240.0/24 No ROA Other IRR onlyNTTCOM 2 0%low visibility 2
114.52.241.0/24 No ROA Other IRR onlyNTTCOM 2 0%low visibility 2

AS-SET

AS23990 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 19 are in fix.csv.

  • ROA: none8
  • Route object: none1
  • Route object: RIR7
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none114.52.243.0/24No ROA covers it. Add a ROA for AS23990, maxLength 24.2 of 673
Route object: none114.52.243.0/24Route objects for it name AS18302. Add a route object with origin AS23990 in the RIR database for the space.2 of 673
ROA: none58.102.226.0/24No ROA covers it. Add a ROA for AS23990, maxLength 24.2 of 673
Route object: RIR58.102.226.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.2 of 673
ROA: none61.104.42.0/24No ROA covers it. Add a ROA for AS23990, maxLength 24.2 of 673
Route object: RIR61.104.42.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none61.104.43.0/24No ROA covers it. Add a ROA for AS23990, maxLength 24.2 of 673
Route object: RIR61.104.43.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none61.104.45.0/24No ROA covers it. Add a ROA for AS23990, maxLength 24.2 of 673
Route object: RIR61.104.45.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none114.52.239.0/24No ROA covers it. Add a ROA for AS23990, maxLength 24.2 of 673
Route object: RIR114.52.239.0/24Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673
ROA: none114.52.240.0/24No ROA covers it. Add a ROA for AS23990, maxLength 24.2 of 673
Route object: RIR114.52.240.0/24Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673
ROA: none114.52.241.0/24No ROA covers it. Add a ROA for AS23990, maxLength 24.2 of 673
Route object: RIR114.52.241.0/24Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

58.102.0.0/15RADBNo ROA
61.100.35.0/24RADBNo ROA
61.100.42.0/23RADBNo 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.