LAYER3 INTEL
Get started
Sign in
Data as of Nov 15, 2026

192.169.80.0/20

7 anonymizer addresses · 0.17% · VPN4 residential-proxy exits · 30 days

Limestone Networks, Inc.

Announcement
this exact prefix
RPKI valid
Announced by
AS46475
Type
Hosting
>99% of it

Residential-proxy exits

Proxy exits
4
0.10% of its addresses · 30 days
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

58 observations
IPv4 market

Path

1 · Holder
Limestone Networks, Inc.
record created Nov 2, 2012
2 · Leased from
not leased
3 · Announced by
AS46475 Limestone Networks, Inc.
since Jun 2023 · 3.4 yr ago
4 · Use
VPN servicesnamed TunnelBear
Hosting

Operators, sellers and brokers

VPN services

NameParentIn 192.169.80.0/20/24s
TunnelBearMcAfee
70.17%
1

Lineage

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

192.169.80.0/20

From the registry to its use

  1. Nov 2, 2012
    Registry record
    Limestone Networks, Inc.
    Direct Allocation
    192.169.80.0/20
  2. Mar 12, 2013
    Route object
    AS46475 Limestone Networks, Inc.
    ARIN route object for AS46475 Limestone Networks, Inc., maintainer MNT-LIMES-2
  3. Mar 22, 2013– Dec 17, 2022
    Announced
    AS46475 Limestone Networks, Inc.
    Hosting
  4. Aug 25, 2014
    Route object
    AS46475 Limestone Networks, Inc.
    RADB route object for AS46475 Limestone Networks, Inc., maintainer MAINT-AS1828
  5. Aug 25, 2014
    Route object
    AS46475 Limestone Networks, Inc.
    RADB route object for AS46475 Limestone Networks, Inc., maintainer MAINT-AS1828
    192.169.92.0/22
  6. Dec 6, 2022– Jun 27, 2023
    Announced
    AS397666 HostRound LLC
    Hosting
  7. Jun 16, 2023– today
    Announced
    AS46475 Limestone Networks, Inc.
    Hosting
  8. today
    Used
    TunnelBear
    VPN

Announcements

Nesting

More-specifics by size

Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific

Announcements inside

PrefixOriginTypeAnonymizer addressesOperatorHolderRPKI
192.169.80.0/22
since Jan 2026
AS46475HostingLimestone Networks, Inc.
192.169.82.0/24
since Aug 2021
AS46475HostingLimestone Networks, Inc.
192.169.84.0/24
since Jan 2026
AS46475HostingLimestone Networks, Inc.
192.169.85.0/24
since Nov 2018
AS46475HostingLimestone Networks, Inc.
192.169.86.0/24
since Nov 2019
AS46475HostingLimestone Networks, Inc.
192.169.87.0/24
since Nov 2019
AS46475HostingLimestone Networks, Inc.
192.169.88.0/24
since Apr 2020
AS46475HostingLimestone Networks, Inc.
192.169.89.0/24
since Dec 2021
AS46475HostingLimestone Networks, Inc.
192.169.90.0/24
since May 2022
AS46475Hosting72.7%VPNVPN servicesoperated by TunnelBearLimestone Networks, Inc.
192.169.92.0/23
since Jul 2026
AS46475HostingLimestone Networks, Inc.
192.169.93.0/24
since Aug 2021
AS46475HostingLimestone Networks, Inc.
192.169.94.0/24
since Jan 2026
AS46475HostingLimestone Networks, Inc.
192.169.95.0/24
since Apr 2022
AS46475HostingLimestone Networks, Inc.

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
192.169.80.0/204,096LIMESTONE-NETWORKSLimestone Networks, Inc. (LIMES-2) · USDirect AllocationNov 2, 2012abuse@limestonenetworks.com
└ 192.169.80.0/304SERCAN-1unknown———
└ 192.169.80.12/304LSN-DLLSTX-1unknown———
└ 192.169.80.16/304RSS-NETBLKC-192-169-80-16unknown———
└ 192.169.80.32/304LSN-DLLSTX-1unknown———
└ 192.169.80.36/312LSN-DLLSTX-1unknown———
└ 192.169.80.40/298LSN-DLLSTX-1unknown———
└ 192.169.80.52/304LSN-DLLSTX-1unknown———
└ 192.169.80.84/304LSN-DLLSTX-1unknown———
└ 192.169.80.88/304LSN-DLLSTX-1unknown———
└ 192.169.80.92/304LSN-DLLSTX-1unknown———
└ 192.169.80.100/304LSN-DLLSTX-1unknown———
└ 192.169.80.104/298LSN-DLLSTX-1unknown———
└ 192.169.80.208/298LSN-DLLSTX-1unknown———
└ 192.169.80.224/2732LSN-DLLSTX-1unknown———
└ 192.169.81.32/304LSN-DLLSTX-1unknown———
└ 192.169.81.40/304LSN-DLLSTX-1unknown———
└ 192.169.81.56/298PING-1unknown———
└ 192.169.81.96/2732LSN-DLLSTX-1unknown———
└ 192.169.81.168/304LSN-DLLSTX-1unknown———
└ 192.169.81.176/298PING-1unknown———
└ 192.169.81.192/298PING-1unknown———
└ 192.169.81.220/304LSN-DLLSTX-1unknown———
└ 192.169.81.240/304LSN-DLLSTX-1unknown———
└ 192.169.81.244/304LSN-DLLSTX-1unknown———
└ 192.169.82.16/298LSN-DLLSTX-1unknown———
└ 192.169.82.120/298LSN-DLLSTX-1unknown———
└ 192.169.82.144/298PING-1unknown———
└ 192.169.82.184/298LSN-DLLSTX-1unknown———
└ 192.169.82.192/304LSN-DLLSTX-1unknown———
└ 192.169.82.224/304LSN-DLLSTX-1unknown———
└ 192.169.82.240/304LSN-DLLSTX-1unknown———
└ 192.169.83.8/298LSN-DLLSTX-1unknown———
└ 192.169.83.32/298PING-1unknown———
└ 192.169.83.200/298LSN-DLLSTX-1unknown———
└ 192.169.85.96/298LSN-DLLSTX-1unknown———
└ 192.169.85.108/304LSN-DLLSTX-1unknown———
└ 192.169.85.160/298LSN-DLLSTX-1unknown———
└ 192.169.86.8/304LSN-DLLSTX-1unknown———
└ 192.169.86.16/298LSN-DLLSTX-1unknown———
└ 192.169.86.44/304LSN-DLLSTX-1unknown———
└ 192.169.86.48/298LSN-DLLSTX-1unknown———
└ 192.169.86.104/298LSN-DLLSTX-1unknown———
└ 192.169.86.144/298LSN-DLLSTX-1unknown———
└ 192.169.86.160/2816LSN-DLLSTX-1unknown———
└ 192.169.87.16/298LSN-DLLSTX-1unknown———
└ 192.169.87.128/298LSN-DLLSTX-1unknown———
└ 192.169.88.0/2732LSN-DLLSTX-1unknown———
└ 192.169.88.48/298LSN-DLLSTX-1unknown———
└ 192.169.88.64/298LSN-DLLSTX-1unknown———
└ 192.169.88.72/298LSN-DLLSTX-1unknown———
└ 192.169.88.216/298LSN-DLLSTX-1unknown———
└ 192.169.89.4/304LSN-DLLSTX-1unknown———
└ 192.169.89.8/298LSN-DLLSTX-1unknown———
└ 192.169.89.16/298LSN-DLLSTX-1unknown———
└ 192.169.89.24/298LSN-DLLSTX-1unknown———
└ 192.169.89.48/298PING-1unknown———
└ 192.169.89.104/298LSN-DLLSTX-1unknown———
└ 192.169.89.160/304LSN-DLLSTX-1unknown———
└ 192.169.89.164/304LSN-DLLSTX-1unknown———
└ 192.169.89.168/304LSN-DLLSTX-1unknown———
└ 192.169.89.172/304LSN-DLLSTX-1unknown———
└ 192.169.89.176/304LSN-DLLSTX-1unknown———
└ 192.169.89.180/304LSN-DLLSTX-1unknown———
└ 192.169.89.188/304LSN-DLLSTX-1unknown———
└ 192.169.89.196/304LSN-DLLSTX-1unknown———
└ 192.169.89.200/304LSN-DLLSTX-1unknown———
└ 192.169.89.204/304LSN-DLLSTX-1unknown———
└ 192.169.90.0/2816LSN-DLLSTX-1unknown———
└ 192.169.90.16/2816LSN-DLLSTX-1unknown———
└ 192.169.90.32/2816LSN-DLLSTX-1unknown———
└ 192.169.90.48/304LSN-DLLSTX-1unknown———
└ 192.169.90.54/312LSN-DLLSTX-1unknown———
└ 192.169.90.60/312LSN-DLLSTX-1unknown———
└ 192.169.90.62/312LSN-DLLSTX-1unknown———
└ 192.169.90.80/298LSN-DLLSTX-1unknown———
└ 192.169.90.88/298LSN-DLLSTX-1unknown———
└ 192.169.90.96/298LSN-DLLSTX-1unknown———
└ 192.169.90.104/298LSN-DLLSTX-1unknown———
└ 192.169.90.168/298LSN-DLLSTX-1unknown———
└ 192.169.90.176/312LSN-DLLSTX-1unknown———
└ 192.169.90.180/312LSN-DLLSTX-1unknown———
└ 192.169.90.200/298LSN-DLLSTX-1unknown———
└ 192.169.90.216/312LSN-DLLSTX-1unknown———
└ 192.169.90.218/312LSN-DLLSTX-1unknown———
└ 192.169.90.224/2816LSN-DLLSTX-1unknown———
└ 192.169.92.4/304LSN-DLLSTX-1unknown———
└ 192.169.92.24/298LSN-DLLSTX-1unknown———
└ 192.169.92.40/298PING-1unknown———
└ 192.169.92.224/298LSN-DLLSTX-1unknown———
└ 192.169.92.232/298LSN-DLLSTX-1unknown———
└ 192.169.93.168/298LSN-DLLSTX-1unknown———
└ 192.169.93.184/304LSN-DLLSTX-1unknown———
└ 192.169.93.188/304LSN-DLLSTX-1unknown———
└ 192.169.93.192/298LSN-DLLSTX-1unknown———
└ 192.169.93.200/298PING-1unknown———
└ 192.169.93.208/298LSN-DLLSTX-1unknown———
└ 192.169.93.232/298LSN-DLLSTX-1unknown———
└ 192.169.95.0/298LSN-DLLSTX-1unknown———
└ 192.169.95.16/298LSN-DLLSTX-1unknown———
└ 192.169.95.24/298LSN-DLLSTX-1unknown———
└ 192.169.95.40/298LSN-DLLSTX-1unknown———
└ 192.169.95.64/2816LSN-DLLSTX-1unknown———
└ 192.169.95.88/298LSN-DLLSTX-1unknown———
└ 192.169.95.128/298LSN-DLLSTX-1unknown———
└ 192.169.95.144/298LSN-DLLSTX-1unknown———
└ 192.169.95.152/298LSN-DLLSTX-1unknown———
└ 192.169.95.160/298LSN-DLLSTX-1unknown———
└ 192.169.95.176/298LSN-DLLSTX-1unknown———
└ 192.169.95.200/298LSN-DLLSTX-1unknown———
└ 192.169.95.224/298LSN-DLLSTX-1unknown———
└ 192.169.95.232/298LSN-DLLSTX-1unknown———

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

4,096 addresses
TypeAddressesShareRanges
Hosting4,089>99%16
VPNanonymizer70.17%7

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
Mar 2013
Current origin since
Jun 2023 · 3.4 yr
Origin networks
2
Last change of origin
Jun 2023
Recorded history

History

Handoffs
2