bgpreport

Network · data from 2026-11-12

AS4671 KTOA-AS-KR-KR - KTOA

Registry name: KTOA-AS-KR-KR - KTOA, KR · not in PeeringDB

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

Announced routes

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

2401:8ac0:120::/48 No ROA None 606 95% 67
2401:8ac0:100::/48 No ROA None 95 15% 39
2401:8ac0:1c0::/48 No ROA None 95 15% 39
125.131.87.0/25 No ROA None 16 2%low visibility 13
220.75.238.128/25 No ROA None 16 2%low visibility 13
103.55.35.0/27 No ROA None 14 2%low visibility 13
103.55.35.32/27 No ROA None 14 2%low visibility 13
121.134.220.0/27 No ROA None 14 2%low visibility 13
121.134.220.32/27 No ROA None 14 2%low visibility 13
210.91.80.192/26 No ROA None 14 2%low visibility 13
211.38.137.64/26 No ROA None 14 2%low visibility 13
222.106.198.192/28 No ROA None 13 2%low visibility 13
103.55.35.192/29 No ROA None 10 1%low visibility 10
125.131.118.192/29 No ROA None 10 1%low visibility 10
128.134.105.80/29 No ROA None 10 1%low visibility 10

AS-SET

AS4671 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 83 are in fix.csv.

  • ROA: none15
  • Route object: none15
  • Route object: not announced53
ChangePrefix or setDetailFull-table peers
ROA: none2401:8ac0:120::/48No ROA covers it. Add a ROA for AS4671, maxLength 48.606 of 636
Route object: none2401:8ac0:120::/48No route object for it. Add a route object with origin AS4671 in the RIR database for the space.606 of 636
ROA: none2401:8ac0:100::/48No ROA covers it. Add a ROA for AS4671, maxLength 48.95 of 636
Route object: none2401:8ac0:100::/48No route object for it. Add a route object with origin AS4671 in the RIR database for the space.95 of 636
ROA: none2401:8ac0:1c0::/48No ROA covers it. Add a ROA for AS4671, maxLength 48.95 of 636
Route object: none2401:8ac0:1c0::/48No route object for it. Add a route object with origin AS4671 in the RIR database for the space.95 of 636
ROA: none125.131.87.0/25No ROA covers it. Add a ROA for AS4671, maxLength 25.16 of 673
Route object: none125.131.87.0/25No route object for it. Add a route object with origin AS4671 in the RIR database for the space.16 of 673
ROA: none220.75.238.128/25No ROA covers it. Add a ROA for AS4671, maxLength 25.16 of 673
Route object: none220.75.238.128/25No route object for it. Add a route object with origin AS4671 in the RIR database for the space.16 of 673
ROA: none103.55.35.0/27No ROA covers it. Add a ROA for AS4671, maxLength 27.14 of 673
Route object: none103.55.35.0/27No route object for it. Add a route object with origin AS4671 in the RIR database for the space.14 of 673
ROA: none103.55.35.32/27No ROA covers it. Add a ROA for AS4671, maxLength 27.14 of 673
Route object: none103.55.35.32/27No route object for it. Add a route object with origin AS4671 in the RIR database for the space.14 of 673
ROA: none121.134.220.0/27No ROA covers it. Add a ROA for AS4671, maxLength 27.14 of 673
Route object: none121.134.220.0/27No route object for it. Add a route object with origin AS4671 in the RIR database for the space.14 of 673
ROA: none121.134.220.32/27No ROA covers it. Add a ROA for AS4671, maxLength 27.14 of 673
Route object: none121.134.220.32/27No route object for it. Add a route object with origin AS4671 in the RIR database for the space.14 of 673
ROA: none210.91.80.192/26No ROA covers it. Add a ROA for AS4671, maxLength 26.14 of 673
Route object: none210.91.80.192/26No route object for it. Add a route object with origin AS4671 in the RIR database for the space.14 of 673
ROA: none211.38.137.64/26No ROA covers it. Add a ROA for AS4671, maxLength 26.14 of 673
Route object: none211.38.137.64/26No route object for it. Add a route object with origin AS4671 in the RIR database for the space.14 of 673
ROA: none222.106.198.192/28No ROA covers it. Add a ROA for AS4671, maxLength 28.13 of 673
Route object: none222.106.198.192/28No route object for it. Add a route object with origin AS4671 in the RIR database for the space.13 of 673
ROA: none103.55.35.192/29No ROA covers it. Add a ROA for AS4671, maxLength 29.10 of 673
Route object: none103.55.35.192/29No route object for it. Add a route object with origin AS4671 in the RIR database for the space.10 of 673
ROA: none125.131.118.192/29No ROA covers it. Add a ROA for AS4671, maxLength 29.10 of 673
Route object: none125.131.118.192/29No route object for it. Add a route object with origin AS4671 in the RIR database for the space.10 of 673
ROA: none128.134.105.80/29No ROA covers it. Add a ROA for AS4671, maxLength 29.10 of 673
Route object: none128.134.105.80/29No route object for it. Add a route object with origin AS4671 in the RIR database for the space.10 of 673

Route objects not announced

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

115.84.160.0/21RADBNo ROA
125.60.1.0/24RADBNo ROA
125.60.8.0/24RADBNo ROA
125.60.16.0/24RADBNo ROA
125.60.29.0/24RADBNo ROA
152.99.0.0/16RADBNo ROA
152.99.0.0/17RADBNo ROA
152.99.128.0/18RADBNo ROA
152.99.192.0/19RADBNo ROA
152.99.224.0/19RADBNo ROA
168.126.120.0/24RADBNo ROA
168.126.121.0/24RADBNo ROA
168.126.122.0/24RADBNo ROA
168.126.123.0/24RADBNo ROA
210.95.219.0/24RADBNo ROA
210.97.27.0/24RADBNo ROA
210.99.24.0/24RADBNo ROA
210.99.25.0/24RADBNo ROA
210.99.48.0/24RADBNo ROA
210.99.49.0/24RADBNo ROA
210.99.50.0/24RADBNo ROA
210.99.51.0/24RADBNo ROA
210.99.52.0/24RADBNo ROA
210.99.53.0/24RADBNo ROA
210.99.54.0/24RADBNo ROA
210.99.55.0/24RADBNo ROA
210.99.62.0/24RADBNo ROA
210.103.63.0/24NTTCOM, RADBNo ROA
210.103.72.0/24RADBNo ROA
210.103.81.0/24RADBNo ROA
210.103.82.0/24RADBNo ROA
210.103.83.0/24RADBNo ROA
210.104.41.0/24RADBNo ROA
210.104.148.0/24RADBNo ROA
210.104.249.0/24RADBNo ROA
210.104.250.0/24RADBNo ROA
210.106.108.0/24RADBNo ROA
210.178.100.0/24RADBNo ROA
210.178.101.0/24RADBNo ROA
210.179.148.0/24RADBNo ROA
211.39.76.0/24RADBNo ROA
211.39.94.0/24RADBNo ROA
211.57.153.0/24RADBNo ROA
211.114.24.0/24RADBNo ROA
211.168.120.0/22RADBNo ROA
211.184.197.0/24NTTCOM, RADBNo ROA
211.252.37.0/24RADBNo ROA
211.252.203.0/24RADBNo ROA
211.253.60.0/24RADBNo ROA
211.253.61.0/24RADBNo ROA
211.253.121.0/24RADBNo ROA
211.253.122.0/24RADBNo ROA
211.253.124.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.