bgpreport

Network · data from 2026-11-12

AS395506 KN-DFW-ASN - KODIAK NETWORKS, INC.

Registry name: KN-DFW-ASN - KODIAK NETWORKS, INC., US · not in PeeringDB

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

Announced routes

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

67.212.9.0/24 Invalid: origin Other origin only 22 3%low visibility 17
67.212.13.0/24 Invalid: origin Other origin only 22 3%low visibility 17
67.212.14.0/24 Invalid: origin Other origin only 22 3%low visibility 17
192.151.140.0/24 Invalid: origin Other origin only 22 3%low visibility 17
199.47.228.0/24 Invalid: origin Other origin only 22 3%low visibility 17
2620:129:9004::/48 Invalid: origin Other origin only 1 0%low visibility 1
63.161.7.0/24 No ROA None 673 100% 67
63.161.75.0/24 No ROA None 673 100% 67
199.47.95.0/24 No ROA Other origin only 673 100% 67
212.69.147.0/24 No ROA None 673 100% 67
2600:3:1::/48 No ROA None 605 95% 67
2600:4:402::/48 No ROA None 605 95% 67
2607:ffd0:303::/48 No ROA Other IRR onlyRADB 634 100% 68
76.8.20.0/24 Valid Other IRR onlyRADB 671 100% 67
76.8.27.0/24 Valid Other IRR onlyRADB 671 100% 67
2620:129:9003::/48 Valid RIR databaseARIN, RADB 636 100% 67
2620:129:9005::/48 Valid RIR databaseARIN 635 100% 67
142.147.79.0/24 Valid RIR databaseARIN, RADB 35 5%low visibility 21

AS-SET

AS395506 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 31 are in fix.csv.

  • ROA: origin6
  • ROA: none7
  • Route object: none12
  • Route object: RIR3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin67.212.9.0/24ROAs covering it name AS17216, not AS395506. If AS395506 should announce it, add a ROA for AS395506.22 of 673
Route object: none67.212.9.0/24Route objects for it name AS17216. Add a route object with origin AS395506 in the RIR database for the space.22 of 673
ROA: origin67.212.13.0/24ROAs covering it name AS17216, not AS395506. If AS395506 should announce it, add a ROA for AS395506.22 of 673
Route object: none67.212.13.0/24Route objects for it name AS17216. Add a route object with origin AS395506 in the RIR database for the space.22 of 673
ROA: origin67.212.14.0/24ROAs covering it name AS17216, not AS395506. If AS395506 should announce it, add a ROA for AS395506.22 of 673
Route object: none67.212.14.0/24Route objects for it name AS17216. Add a route object with origin AS395506 in the RIR database for the space.22 of 673
ROA: origin192.151.140.0/24ROAs covering it name AS17216, not AS395506. If AS395506 should announce it, add a ROA for AS395506.22 of 673
Route object: none192.151.140.0/24Route objects for it name AS17216. Add a route object with origin AS395506 in the RIR database for the space.22 of 673
ROA: origin199.47.228.0/24ROAs covering it name AS17216, not AS395506. If AS395506 should announce it, add a ROA for AS395506.22 of 673
Route object: none199.47.228.0/24Route objects for it name AS17216. Add a route object with origin AS395506 in the RIR database for the space.22 of 673
ROA: origin2620:129:9004::/48ROAs covering it name AS13767, not AS395506. If AS395506 should announce it, add a ROA for AS395506.1 of 636
Route object: none2620:129:9004::/48Route objects for it name AS13767. Add a route object with origin AS395506 in the RIR database for the space.1 of 636
ROA: none63.161.7.0/24No ROA covers it. Add a ROA for AS395506, maxLength 24.673 of 673
Route object: none63.161.7.0/24No route object for it. Add a route object with origin AS395506 in the RIR database for the space.673 of 673
ROA: none63.161.75.0/24No ROA covers it. Add a ROA for AS395506, maxLength 24.673 of 673
Route object: none63.161.75.0/24No route object for it. Add a route object with origin AS395506 in the RIR database for the space.673 of 673
ROA: none199.47.95.0/24No ROA covers it. Add a ROA for AS395506, maxLength 24.673 of 673
Route object: none199.47.95.0/24Route objects for it name AS17216. Add a route object with origin AS395506 in the RIR database for the space.673 of 673
ROA: none212.69.147.0/24No ROA covers it. Add a ROA for AS395506, maxLength 24.673 of 673
Route object: none212.69.147.0/24No route object for it. Add a route object with origin AS395506 in the RIR database for the space.673 of 673
ROA: none2600:3:1::/48No ROA covers it. Add a ROA for AS395506, maxLength 48.605 of 636
Route object: none2600:3:1::/48No route object for it. Add a route object with origin AS395506 in the RIR database for the space.605 of 636
ROA: none2600:4:402::/48No ROA covers it. Add a ROA for AS395506, maxLength 48.605 of 636
Route object: none2600:4:402::/48No route object for it. Add a route object with origin AS395506 in the RIR database for the space.605 of 636
ROA: none2607:ffd0:303::/48No ROA covers it. Add a ROA for AS395506, maxLength 48.634 of 636
Route object: RIR2607:ffd0:303::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR76.8.20.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR76.8.27.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

76.8.26.0/23RADBValid
76.8.26.0/24RADBValid
162.254.28.0/24ARIN, RADBValid

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.