bgpreport

Network · data from 2026-11-12

AS26914 Synoptek

Registry name: SYNOPTEK - Synoptek, LLC, US · PeeringDB

31IPv4 routes 87.1% RPKI valid · 100.0% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
25Route objects not announced registered with origin AS26914, seen from no peer

Announced routes

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

64.79.149.0/24 No ROA Other IRR onlyALTDB, RADB 673 100% 67
208.79.34.0/23 No ROA Other IRR onlyALTDB, RADB 673 100% 67
216.115.79.0/24 No ROA Other IRR onlyALTDB, RADB 673 100% 67
216.115.86.0/23 No ROA Other IRR onlyALTDB, RADB 673 100% 67
64.147.160.0/22 Valid Other IRR onlyRADB 673 100% 67
166.93.0.0/16 Valid Other IRR onlyRADB 673 100% 67
2001:1898:8001::/48 Valid Other IRR onlyRADB 635 100% 67
64.127.122.0/24 Valid RIR databaseARIN 673 100% 67
64.147.188.0/22 Valid RIR databaseARIN, RADB 673 100% 67
69.80.192.0/20 Valid RIR databaseALTDB, ARIN, RADB 673 100% 67
69.80.213.0/24 Valid RIR databaseARIN 673 100% 67
69.80.216.0/24 Valid RIR databaseARIN 673 100% 67
69.80.217.0/24 Valid RIR databaseARIN 673 100% 67
69.80.218.0/24 Valid RIR databaseARIN 673 100% 67
69.80.222.0/24 Valid RIR databaseARIN 673 100% 67
166.93.0.0/20 Valid RIR databaseARIN, RADB 673 100% 67
166.93.143.0/24 Valid RIR databaseARIN 673 100% 67
204.56.48.0/24 Valid RIR databaseARIN, RADB 673 100% 67
204.227.0.0/24 Valid RIR databaseARIN, RADB 673 100% 67
204.227.1.0/24 Valid RIR databaseARIN, RADB 673 100% 67
204.227.4.0/24 Valid RIR databaseARIN, RADB 673 100% 67
204.227.6.0/24 Valid RIR databaseARIN, RADB 673 100% 67
204.227.26.0/24 Valid RIR databaseARIN, RADB 673 100% 67
72.172.226.0/24 Valid RIR databaseARIN 671 100% 68
72.172.229.0/24 Valid RIR databaseARIN 671 100% 68
72.172.231.0/24 Valid RIR databaseARIN 671 100% 68
72.172.233.0/24 Valid RIR databaseARIN 671 100% 68
72.172.234.0/24 Valid RIR databaseARIN 671 100% 68
72.172.235.0/24 Valid RIR databaseARIN 671 100% 68
72.172.236.0/24 Valid RIR databaseARIN 671 100% 68
72.172.239.0/24 Valid RIR databaseARIN 671 100% 67
72.172.232.0/24 Valid RIR databaseARIN 670 100% 68
2001:1898:2400::/40 Valid RIR databaseARIN 635 100% 67
2001:1898:3200::/40 Valid RIR databaseARIN, RADB 635 100% 68

AS-SET

AS26914's PeeringDB record names no 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 36 are in fix.csv.

  • ROA: none4
  • Route object: RIR7
  • Route object: not announced25
ChangePrefix or setDetailFull-table peers
ROA: none64.79.149.0/24No ROA covers it. Add a ROA for AS26914, maxLength 24.673 of 673
Route object: RIR64.79.149.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
ROA: none208.79.34.0/23No ROA covers it. Add a ROA for AS26914, maxLength 23.673 of 673
Route object: RIR208.79.34.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.115.79.0/24No ROA covers it. Add a ROA for AS26914, maxLength 24.673 of 673
Route object: RIR216.115.79.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.115.86.0/23No ROA covers it. Add a ROA for AS26914, maxLength 23.673 of 673
Route object: RIR216.115.86.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR64.147.160.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR166.93.0.0/16Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2001:1898:8001::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

64.127.96.0/19ALTDB, RADBValid
64.147.160.0/19ALTDBValid
64.147.161.0/24ARIN, RADBValid
66.32.88.0/21RADBValid
66.116.120.64/26ALTDB, RADBNo ROA
69.80.192.0/19ALTDBValid
69.80.208.0/21RADBValid
69.80.216.0/21ARIN, RADBValid
69.80.220.0/24ARINValid
72.172.224.0/19ALTDBValid
72.172.224.0/20ALTDBValid
72.172.248.0/21ALTDBValid
77.95.24.0/22RIPENo ROA
103.12.92.0/23RADBNo ROA
103.12.92.0/24RADBNo ROA
103.12.93.0/24RADBNo ROA
103.12.94.0/23RADBNo ROA
103.12.94.0/24RADBNo ROA
103.12.95.0/24RADBNo ROA
166.93.112.0/20ARINValid
204.56.32.0/19RADBValid
204.227.0.0/19RADBValid
2001:1898::/32RADBValid
2001:1898:2800::/40ARINValid
2001:1898:8001::/60ARINValid

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.