Network · data from 2026-11-12

AS38679 FDKRELAY-AS-KR-KR - KPN

Registry name: FDKRELAY-AS-KR-KR - KPN, KR · not in PeeringDB

7IPv4 routes 0.0% RPKI valid · 14.3% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

7No ROA 6 with no route object for this origin

6Low visibility seen by under 10% of full-table peers

37Route objects not announced registered with origin AS38679, seen from no peer

Announced routes

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


1.232.153.128/25	No ROA	None	16 2%low visibility	13
1.232.231.192/26	No ROA	None	14 2%low visibility	13
114.201.208.128/27	No ROA	None	14 2%low visibility	13
222.110.185.192/27	No ROA	None	14 2%low visibility	13
1.232.3.160/27	No ROA	None	3 0%low visibility	3
218.49.227.0/26	No ROA	None	3 0%low visibility	3
210.113.9.0/24	No ROA	Other IRR onlyRADB	673 100%	67

1.232.153.128/25

No ROA

None

16 2%low visibility

1.232.231.192/26

No ROA

None

14 2%low visibility

114.201.208.128/27

No ROA

None

14 2%low visibility

222.110.185.192/27

No ROA

None

14 2%low visibility

1.232.3.160/27

No ROA

None

3 0%low visibility

218.49.227.0/26

No ROA

None

3 0%low visibility

210.113.9.0/24

No ROA

Other IRR onlyRADB

673 100%

AS-SET

AS38679 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 51 are in fix.csv.

ROA: none7
Route object: none6
Route object: RIR1
Route object: not announced37

Change	Prefix or set	Detail	Full-table peers
ROA: none	1.232.153.128/25	No ROA covers it. Add a ROA for AS38679, maxLength 25.	16 of 673
Route object: none	1.232.153.128/25	No route object for it. Add a route object with origin AS38679 in the RIR database for the space.	16 of 673
ROA: none	1.232.231.192/26	No ROA covers it. Add a ROA for AS38679, maxLength 26.	14 of 673
Route object: none	1.232.231.192/26	No route object for it. Add a route object with origin AS38679 in the RIR database for the space.	14 of 673
ROA: none	114.201.208.128/27	No ROA covers it. Add a ROA for AS38679, maxLength 27.	14 of 673
Route object: none	114.201.208.128/27	No route object for it. Add a route object with origin AS38679 in the RIR database for the space.	14 of 673
ROA: none	222.110.185.192/27	No ROA covers it. Add a ROA for AS38679, maxLength 27.	14 of 673
Route object: none	222.110.185.192/27	No route object for it. Add a route object with origin AS38679 in the RIR database for the space.	14 of 673
ROA: none	1.232.3.160/27	No ROA covers it. Add a ROA for AS38679, maxLength 27.	3 of 673
Route object: none	1.232.3.160/27	No route object for it. Add a route object with origin AS38679 in the RIR database for the space.	3 of 673
ROA: none	218.49.227.0/26	No ROA covers it. Add a ROA for AS38679, maxLength 26.	3 of 673
Route object: none	218.49.227.0/26	No route object for it. Add a route object with origin AS38679 in the RIR database for the space.	3 of 673
ROA: none	210.113.9.0/24	No ROA covers it. Add a ROA for AS38679, maxLength 24.	673 of 673
Route object: RIR	210.113.9.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

1.232.153.128/25

No ROA covers it. Add a ROA for AS38679, maxLength 25.

16 of 673

Route object: none

1.232.153.128/25

No route object for it. Add a route object with origin AS38679 in the RIR database for the space.

16 of 673

ROA: none

1.232.231.192/26

No ROA covers it. Add a ROA for AS38679, maxLength 26.

14 of 673

Route object: none

1.232.231.192/26

No route object for it. Add a route object with origin AS38679 in the RIR database for the space.

14 of 673

ROA: none

114.201.208.128/27

No ROA covers it. Add a ROA for AS38679, maxLength 27.

14 of 673

Route object: none

114.201.208.128/27

No route object for it. Add a route object with origin AS38679 in the RIR database for the space.

14 of 673

ROA: none

222.110.185.192/27

No ROA covers it. Add a ROA for AS38679, maxLength 27.

14 of 673

Route object: none

222.110.185.192/27

No route object for it. Add a route object with origin AS38679 in the RIR database for the space.

14 of 673

ROA: none

1.232.3.160/27

No ROA covers it. Add a ROA for AS38679, maxLength 27.

3 of 673

Route object: none

1.232.3.160/27

No route object for it. Add a route object with origin AS38679 in the RIR database for the space.

3 of 673

ROA: none

218.49.227.0/26

No ROA covers it. Add a ROA for AS38679, maxLength 26.

3 of 673

Route object: none

218.49.227.0/26

No route object for it. Add a route object with origin AS38679 in the RIR database for the space.

3 of 673

ROA: none

210.113.9.0/24

No ROA covers it. Add a ROA for AS38679, maxLength 24.

673 of 673

Route object: RIR

210.113.9.0/24

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route objects not announced

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


49.246.64.0/22	NTTCOM	No ROA
49.246.68.0/22	NTTCOM	No ROA
49.246.72.0/22	NTTCOM	No ROA
49.246.76.0/22	NTTCOM	No ROA
49.246.80.0/22	NTTCOM	No ROA
49.246.84.0/22	NTTCOM	No ROA
49.246.88.0/22	NTTCOM	No ROA
49.246.92.0/22	NTTCOM	No ROA
49.246.96.0/22	NTTCOM	No ROA
49.246.100.0/22	NTTCOM	No ROA
49.246.104.0/22	NTTCOM	No ROA
49.246.108.0/22	NTTCOM	No ROA
49.246.112.0/22	NTTCOM	No ROA
49.246.116.0/22	NTTCOM	No ROA
49.246.120.0/22	NTTCOM	No ROA
49.246.124.0/22	NTTCOM	No ROA
112.121.192.0/22	NTTCOM, RADB	No ROA
112.121.196.0/22	NTTCOM, RADB	No ROA
112.121.200.0/22	NTTCOM, RADB	No ROA
112.121.204.0/22	NTTCOM, RADB	No ROA
112.121.208.0/22	NTTCOM, RADB	No ROA
112.121.212.0/22	NTTCOM, RADB	No ROA
112.121.216.0/22	NTTCOM, RADB	No ROA
112.121.220.0/22	NTTCOM, RADB	No ROA
112.121.224.0/22	NTTCOM, RADB	No ROA
112.121.228.0/22	NTTCOM, RADB	No ROA
112.121.232.0/22	NTTCOM, RADB	No ROA
112.121.236.0/22	NTTCOM, RADB	No ROA
112.121.240.0/22	NTTCOM, RADB	No ROA
112.121.244.0/22	NTTCOM, RADB	No ROA
112.121.248.0/22	NTTCOM, RADB	No ROA
112.121.252.0/22	NTTCOM, RADB	No ROA
120.29.128.0/20	RADB	No ROA
120.29.128.0/22	RADB	No ROA
120.29.132.0/22	RADB	No ROA
120.29.136.0/22	RADB	No ROA
120.29.140.0/22	RADB	No ROA

49.246.64.0/22

NTTCOM

No ROA

49.246.68.0/22

NTTCOM

No ROA

49.246.72.0/22

NTTCOM

No ROA

49.246.76.0/22

NTTCOM

No ROA

49.246.80.0/22

NTTCOM

No ROA

49.246.84.0/22

NTTCOM

No ROA

49.246.88.0/22

NTTCOM

No ROA

49.246.92.0/22

NTTCOM

No ROA

49.246.96.0/22

NTTCOM

No ROA

49.246.100.0/22

NTTCOM

No ROA

49.246.104.0/22

NTTCOM

No ROA

49.246.108.0/22

NTTCOM

No ROA

49.246.112.0/22

NTTCOM

No ROA

49.246.116.0/22

NTTCOM

No ROA

49.246.120.0/22

NTTCOM

No ROA

49.246.124.0/22

NTTCOM

No ROA

112.121.192.0/22

NTTCOM, RADB

No ROA

112.121.196.0/22

NTTCOM, RADB

No ROA

112.121.200.0/22

NTTCOM, RADB

No ROA

112.121.204.0/22

NTTCOM, RADB

No ROA

112.121.208.0/22

NTTCOM, RADB

No ROA

112.121.212.0/22

NTTCOM, RADB

No ROA

112.121.216.0/22

NTTCOM, RADB

No ROA

112.121.220.0/22

NTTCOM, RADB

No ROA

112.121.224.0/22

NTTCOM, RADB

No ROA

112.121.228.0/22

NTTCOM, RADB

No ROA

112.121.232.0/22

NTTCOM, RADB

No ROA

112.121.236.0/22

NTTCOM, RADB

No ROA

112.121.240.0/22

NTTCOM, RADB

No ROA

112.121.244.0/22

NTTCOM, RADB

No ROA

112.121.248.0/22

NTTCOM, RADB

No ROA

112.121.252.0/22

NTTCOM, RADB

No ROA

120.29.128.0/20

RADB

No ROA

120.29.128.0/22

RADB

No ROA

120.29.132.0/22

RADB

No ROA

120.29.136.0/22

RADB

No ROA

120.29.140.0/22

RADB

No 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.