Data as of Nov 10, 2026

166.93.0.0/20

No anonymizer space · no proxy exits in 30 days

Synoptek, LLC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium
IPv4 market

Path

1 · Holder
Synoptek, LLC
record created Feb 18, 2020
2 · Leased from
3 · Announced by
AS26914 Synoptek, LLC
since May 2024 · 2.5 yr ago
4 · Use
Hosting

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

166.93.0.0/20

From the registry to its use

  1. May 9, 2005– Jun 6, 2020
    Announced
    AS23537 Synoptek, LLC
    as part of 166.93.0.0/16
    166.93.0.0/16
  2. Feb 18, 2020
    Registry record
    Synoptek, LLC
    Direct Allocation
    166.93.0.0/16
  3. Mar 22, 2021– today
    Announced
    AS26914 Synoptek, LLC
    as part of 166.93.0.0/16
    166.93.0.0/16
  4. Mar 29, 2022– Feb 15, 2023
    Announced
    AS26914 Synoptek, LLC
    Business
  5. Mar 30, 2022
    Assigned
    Synoptek Pittsford DC
    Reassigned
    166.93.0.0/20
  6. May 3, 2022
    Route object
    AS26914 Synoptek, LLC
    ARIN route object for AS26914 Synoptek, LLC, maintainer MNT-SL-1189
  7. May 17, 2024– today
    Announced
    AS26914 Synoptek, LLC
    Business
  8. Mar 24, 2025
    Route object
    AS26914 Synoptek, LLC
    RADB route object for AS26914 Synoptek, LLC, maintainer MAINT-AS27506
  9. today
    Leased from
    IPv4.Global
    IP broker

Announcements

Less specific

Covering announcements

PrefixOriginTypeLeased fromHolderRPKI
166.93.0.0/16
since Mar 2021
AS26914BusinessIP broker IPv4.GlobalSynoptek, LLC

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
166.93.0.0/1665,536SYNOPTEK-166-93Synoptek, LLC (SL-1189) · USDirect AllocationFeb 18, 2020service@synoptek.com
└ 166.93.0.0/204,096SYNOPTEK-PITTSFORD-01Synoptek Pittsford DC (C08282435) · USReassignedMar 30, 2022service@synoptek.com
via SYNOPTEK-166-93

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Mar 2022
Current origin since
May 2024 · 2.5 yr
Origin networks
1