bgpreport

Network · data from 2026-11-12

AS216475 nktelecom NKtelecom INC

Registry name: nktelecom NKtelecom INC, US · not in PeeringDB

33IPv4 routes 84.8% RPKI valid · 81.8% with a route object
6IPv6 routes 33.3% RPKI valid · 100.0% with a route object
3RPKI invalid 3 origin · 0 maxLength
6No ROA 6 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS216475, seen from no peer

Announced routes

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

185.123.157.0/24 Invalid: origin Other origin only 72 11% 37
151.246.195.0/24 Invalid: origin None 2 0%low visibility 2
165.49.251.0/24 Invalid: origin Other origin only 2 0%low visibility 2
150.251.156.0/24 No ROA None 1 0%low visibility 1
45.8.157.0/24 No ROA RIR databaseRIPE 669 99% 67
2a14:1b84:2000::/48 No ROA RIR databaseRIPE 634 100% 69
2a0c:dd80:2001::/48 No ROA RIR databaseRIPE 633 100% 67
2a14:1b84:3000::/48 No ROA RIR databaseRIPE 633 100% 67
2a14:1b84:1000::/48 No ROA RIR databaseRIPE 631 99% 67
213.108.198.0/24 Valid None 672 100% 66
2.27.64.0/22 Valid None 1 0%low visibility 1
95.81.118.0/24 Valid RIR databaseRIPE 672 100% 66
185.136.243.0/24 Valid RIR databaseRIPE 672 100% 66
192.67.161.0/24 Valid RIR databaseARIN 672 100% 66
2.26.138.0/24 Valid RIR databaseRIPE 671 100% 67
5.252.118.0/24 Valid RIR databaseRIPE 671 100% 67
31.77.40.0/23 Valid RIR databaseRIPE 671 100% 67
87.58.211.0/24 Valid RIR databaseRIPE 671 100% 67
93.88.205.0/24 Valid RIR databaseRIPE 671 100% 67
103.27.158.0/24 Valid RIR databaseRIPE 671 100% 67
150.237.78.0/24 Valid RIR databaseRIPE 671 100% 67
150.251.155.0/24 Valid RIR databaseRIPE 671 100% 67
163.5.43.0/24 Valid RIR databaseRIPE 671 100% 67
163.5.157.0/24 Valid RIR databaseRIPE 671 100% 67
194.238.56.0/24 Valid RIR databaseRIPE 671 100% 67
195.133.38.0/24 Valid RIR databaseRIPE 671 100% 67
195.133.79.0/24 Valid RIR databaseRIPE 671 100% 67
195.226.94.0/24 Valid RIR databaseRIPE 671 100% 67
5.253.189.0/24 Valid RIR databaseRIPE 670 100% 67
23.134.216.0/24 Valid RIR databaseARIN 670 100% 67
45.155.164.0/24 Valid RIR databaseRIPE 670 100% 67
46.243.3.0/24 Valid RIR databaseRIPE 670 100% 67
108.165.189.0/24 Valid RIR databaseARIN 670 100% 67
216.238.36.0/23 Valid RIR databaseARIN 670 100% 67
45.112.192.0/24 Valid RIR databaseRIPE 669 99% 67
138.249.98.0/24 Valid RIR databaseRIPE 669 99% 67
2a0c:dd80:3000::/48 Valid RIR databaseRIPE 634 100% 69
2a0c:dd80:2000::/48 Valid RIR databaseRIPE 633 100% 67
94.156.2.0/24 Valid RIR databaseRIPE 28 4%low visibility 22

AS-SET

AS216475 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 21 are in fix.csv.

  • ROA: origin3
  • ROA: none6
  • Route object: none6
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: origin185.123.157.0/24ROAs covering it name AS13335, not AS216475. If AS216475 should announce it, add a ROA for AS216475.72 of 673
Route object: none185.123.157.0/24Route objects for it name AS13335. Add a route object with origin AS216475 in the RIR database for the space.72 of 673
ROA: origin151.246.195.0/24ROAs covering it name AS834, AS211484, not AS216475. If AS216475 should announce it, add a ROA for AS216475.2 of 673
Route object: none151.246.195.0/24No route object for it. Add a route object with origin AS216475 in the RIR database for the space.2 of 673
ROA: origin165.49.251.0/24ROAs covering it name AS834, not AS216475. If AS216475 should announce it, add a ROA for AS216475.2 of 673
Route object: none165.49.251.0/24Route objects for it name AS834. Add a route object with origin AS216475 in the RIR database for the space.2 of 673
ROA: none150.251.156.0/24No ROA covers it. Add a ROA for AS216475, maxLength 24.1 of 673
Route object: none150.251.156.0/24No route object for it. Add a route object with origin AS216475 in the RIR database for the space.1 of 673
ROA: none45.8.157.0/24No ROA covers it. Add a ROA for AS216475, maxLength 24.669 of 673
ROA: none2a14:1b84:2000::/48No ROA covers it. Add a ROA for AS216475, maxLength 48.634 of 636
ROA: none2a0c:dd80:2001::/48No ROA covers it. Add a ROA for AS216475, maxLength 48.633 of 636
ROA: none2a14:1b84:3000::/48No ROA covers it. Add a ROA for AS216475, maxLength 48.633 of 636
ROA: none2a14:1b84:1000::/48No ROA covers it. Add a ROA for AS216475, maxLength 48.631 of 636
Route object: none213.108.198.0/24No route object for it. Add a route object with origin AS216475 in the RIR database for the space.672 of 673
Route object: none2.27.64.0/22No route object for it. Add a route object with origin AS216475 in the RIR database for the space.1 of 673

Route objects not announced

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

2.27.64.0/24RIPEValid
31.77.32.0/23RIPEValid
173.249.165.0/24ARINValid
173.249.167.0/24ARINValid
216.238.36.0/24ARINInvalid: maxLength
216.238.37.0/24ARINInvalid: maxLength

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.