bgpreport

Network · data from 2026-11-12

AS10155 JBCTV

Registry name: KOSME-AS-KR-KR - KOSME, KR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10155, 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.
117.52.165.0/24 No ROA Other IRR onlyRADB 672 100% 67
117.52.164.0/24 No ROA Other IRR onlyRADB 33 5%low visibility 26

AS-SET

AS10155's PeeringDB record names no 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 68 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced64
ChangePrefix or setDetailFull-table peers
ROA: none117.52.165.0/24No ROA covers it. Add a ROA for AS10155, maxLength 24.672 of 673
Route object: RIR117.52.165.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none117.52.164.0/24No ROA covers it. Add a ROA for AS10155, maxLength 24.33 of 673
Route object: RIR117.52.164.0/24Route object only in RADB. Add it in the RIR database for the space.33 of 673

Route objects not announced

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

1.177.108.0/22NTTCOMNo ROA
1.177.112.0/22NTTCOMNo ROA
1.177.116.0/22NTTCOMNo ROA
1.177.120.0/22NTTCOMNo ROA
1.177.124.0/22NTTCOMNo ROA
42.82.64.0/19RADBNo ROA
42.82.64.0/22NTTCOMNo ROA
42.82.68.0/22NTTCOMNo ROA
42.82.72.0/22NTTCOMNo ROA
42.82.76.0/22NTTCOMNo ROA
42.82.80.0/22NTTCOMNo ROA
42.82.84.0/22NTTCOMNo ROA
42.82.88.0/22NTTCOMNo ROA
42.82.92.0/22NTTCOMNo ROA
61.253.213.0/24NTTCOMNo ROA
61.253.217.0/24NTTCOMNo ROA
61.253.218.0/24NTTCOMNo ROA
61.253.219.0/24NTTCOMNo ROA
61.253.240.0/21NTTCOMNo ROA
61.253.249.0/24NTTCOM, RADBNo ROA
61.253.251.0/24NTTCOM, RADBNo ROA
61.253.252.0/24NTTCOM, RADBNo ROA
61.253.253.0/24NTTCOM, RADBNo ROA
61.253.254.0/24NTTCOM, RADBNo ROA
61.253.255.0/24NTTCOM, RADBNo ROA
61.255.118.0/24NTTCOM, RADBNo ROA
110.46.0.0/21NTTCOMNo ROA
110.46.8.0/21NTTCOM, RADBNo ROA
110.46.16.0/21NTTCOMNo ROA
110.46.24.0/21NTTCOMNo ROA
110.46.32.0/21NTTCOM, RADBNo ROA
110.46.40.0/21NTTCOMNo ROA
110.46.48.0/21NTTCOMNo ROA
110.46.56.0/21NTTCOMNo ROA
110.46.64.0/21NTTCOMNo ROA
110.46.72.0/21NTTCOM, RADBNo ROA
110.46.80.0/21NTTCOMNo ROA
110.46.88.0/21NTTCOMNo ROA
113.130.222.0/24NTTCOMNo ROA
113.130.223.0/24NTTCOMNo ROA
203.235.71.0/24RADBNo ROA
203.235.88.0/24RADBNo ROA
203.243.186.0/23RADBNo ROA
203.243.188.0/23RADBNo ROA
203.243.190.0/24RADBNo ROA
210.109.92.0/24RADBNo ROA
210.109.128.0/22RADBNo ROA
210.109.149.0/24RADBNo ROA
210.109.166.0/24RADBNo ROA
210.109.168.0/23RADBNo ROA
210.109.234.0/23RADBNo ROA
210.109.234.0/24RADBNo ROA
210.116.40.0/23RADBNo ROA
210.116.42.0/24RADBNo ROA
211.172.97.0/24NTTCOM, RADBNo ROA
211.172.98.0/24NTTCOM, RADBNo ROA
211.172.99.0/24NTTCOM, RADBNo ROA
211.172.100.0/24NTTCOM, RADBNo ROA
211.172.101.0/24NTTCOM, RADBNo ROA
211.172.102.0/24NTTCOM, RADBNo ROA
211.172.103.0/24NTTCOM, RADBNo ROA
211.255.234.0/23RADBNo ROA
211.255.236.0/22RADBNo ROA
211.255.240.0/23NTTCOM, RADBNo 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.