Network · data from 2026-11-12
AS31841 NKTC - NEW KNOXVILLE TELEPHONE COMPANY
Registry name: NKTC - NEW KNOXVILLE TELEPHONE COMPANY, US · not in PeeringDB
9IPv4 routes
0.0% RPKI valid · 100.0% with a route object
1IPv6 routes
0.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
10No ROA
0 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
117Route objects not announced
registered with origin AS31841, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS31841, 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.
| 69.24.224.0/20 | No ROA | Other IRR onlyRADB | 671 100% |
| 162.250.164.0/22 | No ROA | Other IRR onlyRADB | 671 100% |
| 173.224.192.0/20 | No ROA | Other IRR onlyRADB | 671 100% |
| 199.27.92.0/22 | No ROA | Other IRR onlyRADB | 671 100% |
| 206.51.128.0/19 | No ROA | Other IRR onlyRADB | 671 100% |
| 206.51.157.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 206.51.160.0/20 | No ROA | Other IRR onlyRADB | 671 100% |
| 206.51.176.0/20 | No ROA | Other IRR onlyRADB | 671 100% |
| 2604:3940::/32 | No ROA | Other IRR onlyRADB | 635 100% |
| 74.121.88.0/21 | No ROA | RIR databaseARIN | 671 100% |
AS-SET
AS31841 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 136 are in fix.csv.
- ROA: none10
- Route object: RIR9
- Route object: not announced117
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 69.24.224.0/20 | No ROA covers it. Add a ROA for AS31841, maxLength 20. |
| Route object: RIR | 69.24.224.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 162.250.164.0/22 | No ROA covers it. Add a ROA for AS31841, maxLength 22. |
| Route object: RIR | 162.250.164.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 173.224.192.0/20 | No ROA covers it. Add a ROA for AS31841, maxLength 20. |
| Route object: RIR | 173.224.192.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 199.27.92.0/22 | No ROA covers it. Add a ROA for AS31841, maxLength 22. |
| Route object: RIR | 199.27.92.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.51.128.0/19 | No ROA covers it. Add a ROA for AS31841, maxLength 19. |
| Route object: RIR | 206.51.128.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.51.157.0/24 | No ROA covers it. Add a ROA for AS31841, maxLength 24. |
| Route object: RIR | 206.51.157.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.51.160.0/20 | No ROA covers it. Add a ROA for AS31841, maxLength 20. |
| Route object: RIR | 206.51.160.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.51.176.0/20 | No ROA covers it. Add a ROA for AS31841, maxLength 20. |
| Route object: RIR | 206.51.176.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2604:3940::/32 | No ROA covers it. Add a ROA for AS31841, maxLength 32. |
| Route object: RIR | 2604:3940::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 74.121.88.0/21 | No ROA covers it. Add a ROA for AS31841, maxLength 21. |
Route objects not announced
Route objects with origin AS31841 whose prefix no peer sees AS31841 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 206.51.128.0/18 | RADB | No ROA |
| 206.51.128.0/20 | RADB | No ROA |
| 206.51.128.0/21 | RADB | No ROA |
| 206.51.128.0/22 | RADB | No ROA |
| 206.51.128.0/23 | RADB | No ROA |
| 206.51.128.0/24 | RADB | No ROA |
| 206.51.129.0/24 | RADB | No ROA |
| 206.51.130.0/23 | RADB | No ROA |
| 206.51.130.0/24 | RADB | No ROA |
| 206.51.131.0/24 | RADB | No ROA |
| 206.51.132.0/22 | RADB | No ROA |
| 206.51.132.0/23 | RADB | No ROA |
| 206.51.132.0/24 | RADB | No ROA |
| 206.51.133.0/24 | RADB | No ROA |
| 206.51.134.0/23 | RADB | No ROA |
| 206.51.134.0/24 | RADB | No ROA |
| 206.51.135.0/24 | RADB | No ROA |
| 206.51.136.0/21 | RADB | No ROA |
| 206.51.136.0/22 | RADB | No ROA |
| 206.51.136.0/23 | RADB | No ROA |
| 206.51.136.0/24 | RADB | No ROA |
| 206.51.137.0/24 | RADB | No ROA |
| 206.51.138.0/23 | RADB | No ROA |
| 206.51.138.0/24 | RADB | No ROA |
| 206.51.139.0/24 | RADB | No ROA |
| 206.51.140.0/22 | RADB | No ROA |
| 206.51.140.0/23 | RADB | No ROA |
| 206.51.140.0/24 | RADB | No ROA |
| 206.51.141.0/24 | RADB | No ROA |
| 206.51.142.0/23 | RADB | No ROA |
| 206.51.142.0/24 | RADB | No ROA |
| 206.51.143.0/24 | RADB | No ROA |
| 206.51.144.0/20 | RADB | No ROA |
| 206.51.144.0/21 | RADB | No ROA |
| 206.51.144.0/22 | RADB | No ROA |
| 206.51.144.0/23 | RADB | No ROA |
| 206.51.144.0/24 | RADB | No ROA |
| 206.51.145.0/24 | RADB | No ROA |
| 206.51.146.0/23 | RADB | No ROA |
| 206.51.146.0/24 | RADB | No ROA |
| 206.51.147.0/24 | RADB | No ROA |
| 206.51.148.0/22 | RADB | No ROA |
| 206.51.148.0/23 | RADB | No ROA |
| 206.51.148.0/24 | RADB | No ROA |
| 206.51.149.0/24 | RADB | No ROA |
| 206.51.150.0/23 | RADB | No ROA |
| 206.51.150.0/24 | RADB | No ROA |
| 206.51.151.0/24 | RADB | No ROA |
| 206.51.152.0/21 | RADB | No ROA |
| 206.51.152.0/22 | RADB | No ROA |
| 206.51.152.0/23 | RADB | No ROA |
| 206.51.152.0/24 | RADB | No ROA |
| 206.51.153.0/24 | RADB | No ROA |
| 206.51.154.0/23 | RADB | No ROA |
| 206.51.154.0/24 | RADB | No ROA |
| 206.51.155.0/24 | RADB | No ROA |
| 206.51.156.0/22 | RADB | No ROA |
| 206.51.156.0/23 | RADB | No ROA |
| 206.51.156.0/24 | RADB | No ROA |
| 206.51.158.0/23 | RADB | No ROA |
| 206.51.158.0/24 | RADB | No ROA |
| 206.51.159.0/24 | RADB | No ROA |
| 206.51.160.0/21 | RADB | No ROA |
| 206.51.160.0/22 | RADB | No ROA |
| 206.51.160.0/23 | RADB | No ROA |
| 206.51.160.0/24 | RADB | No ROA |
| 206.51.161.0/24 | RADB | No ROA |
| 206.51.162.0/23 | RADB | No ROA |
| 206.51.162.0/24 | RADB | No ROA |
| 206.51.163.0/24 | RADB | No ROA |
| 206.51.164.0/22 | RADB | No ROA |
| 206.51.164.0/23 | RADB | No ROA |
| 206.51.164.0/24 | RADB | No ROA |
| 206.51.165.0/24 | RADB | No ROA |
| 206.51.166.0/23 | RADB | No ROA |
| 206.51.166.0/24 | RADB | No ROA |
| 206.51.167.0/24 | RADB | No ROA |
| 206.51.168.0/21 | RADB | No ROA |
| 206.51.168.0/22 | RADB | No ROA |
| 206.51.168.0/23 | RADB | No ROA |
| 206.51.168.0/24 | RADB | No ROA |
| 206.51.169.0/24 | RADB | No ROA |
| 206.51.170.0/23 | RADB | No ROA |
| 206.51.170.0/24 | RADB | No ROA |
| 206.51.171.0/24 | RADB | No ROA |
| 206.51.172.0/22 | RADB | No ROA |
| 206.51.172.0/23 | RADB | No ROA |
| 206.51.172.0/24 | RADB | No ROA |
| 206.51.173.0/24 | RADB | No ROA |
| 206.51.174.0/23 | RADB | No ROA |
| 206.51.174.0/24 | RADB | No ROA |
| 206.51.175.0/24 | RADB | No ROA |
| 206.51.176.0/21 | RADB | No ROA |
| 206.51.176.0/22 | RADB | No ROA |
| 206.51.176.0/23 | RADB | No ROA |
| 206.51.176.0/24 | RADB | No ROA |
| 206.51.177.0/24 | RADB | No ROA |
| 206.51.178.0/23 | RADB | No ROA |
| 206.51.178.0/24 | RADB | No ROA |
| 206.51.179.0/24 | RADB | No ROA |
| 206.51.180.0/22 | RADB | No ROA |
| 206.51.180.0/23 | RADB | No ROA |
| 206.51.180.0/24 | RADB | No ROA |
| 206.51.181.0/24 | RADB | No ROA |
| 206.51.182.0/23 | RADB | No ROA |
| 206.51.182.0/24 | RADB | No ROA |
| 206.51.183.0/24 | RADB | No ROA |
| 206.51.184.0/22 | RADB | No ROA |
| 206.51.184.0/23 | RADB | No ROA |
| 206.51.184.0/24 | RADB | No ROA |
| 206.51.185.0/24 | RADB | No ROA |
| 206.51.186.0/23 | RADB | No ROA |
| 206.51.186.0/24 | RADB | No ROA |
| 206.51.187.0/24 | RADB | No ROA |
| 206.51.190.0/23 | RADB | No ROA |
| 206.51.190.0/24 | RADB | No ROA |
| 206.51.191.0/24 | 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.