Data as of Nov 17, 2026

208.115.233.0/24

28 anonymizer addresses · 11% · VPN9 residential-proxy exits · 30 days

Limestone Networks, Inc.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
89% of it

Residential-proxy exits

Proxy exits
9
3.5% of its addresses · 30 days
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

356 observations
IPv4 market

Path

1 · Holder
record created Jan 6, 2010
2 · Leased from
not leased
3 · Announced by
AS46475 Limestone Networks, Inc.
since Mar 2023 · 3.7 yr ago
4 · Use
VPN servicesnamed TunnelBear
Hosting

Operators, sellers and brokers

VPN services

NameParentIn 208.115.233.0/24/24s
TunnelBearMcAfee
2811%
1

Lineage

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

208.115.233.0/24

From the registry to its use

  1. Nov 22, 2006– Oct 8, 2008
    Announced
    AS36377 Comcast Cable Communications, LLC
    as part of 208.115.192.0/18
    208.115.192.0/18
  2. Jan 6, 2010
    Registry record
    Limestone Networks, Inc.
    Direct Allocation
    208.115.192.0/18
  3. Jan 7, 2010– today
    Announced
    AS46475 Limestone Networks, Inc.
    as part of 208.115.192.0/18
    208.115.192.0/18
  4. Mar 12, 2023– today
    Announced
    AS46475 Limestone Networks, Inc.
    Hosting
  5. today
    Used
    TunnelBear
    VPN

Announcements

Less specific

Covering announcements

PrefixOriginTypeHolderRPKI
208.115.192.0/18
since Jan 2010
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
208.115.192.0/1816,384LIMESTONE-NETWORKSLimestone Networks, Inc. (LIMES-2) · USDirect AllocationJan 6, 2010abuse@limestonenetworks.com
└ 208.115.233.0/298LSN-DLLSTX-1unknown———
└ 208.115.233.12/312LSN-DLLSTX-1unknown———
└ 208.115.233.14/312LSN-DLLSTX-1unknown———
└ 208.115.233.16/298LSN-DLLSTX-1unknown———
└ 208.115.233.24/298LSN-DLLSTX-1unknown———
└ 208.115.233.40/298LSN-DLLSTX-1unknown———
└ 208.115.233.48/304LSN-DLLSTX-1unknown———
└ 208.115.233.52/304LSN-DLLSTX-1unknown———
└ 208.115.233.56/298LSN-DLLSTX-1unknown———
└ 208.115.233.128/2816LSN-DLLSTX-1unknown———
└ 208.115.233.152/298LSN-DLLSTX-1unknown———
└ 208.115.233.160/298LSN-DLLSTX-1unknown———
└ 208.115.233.168/298LSN-DLLSTX-1unknown———
└ 208.115.233.176/298LSN-DLLSTX-1unknown———
└ 208.115.233.196/304LSN-DLLSTX-1unknown———
└ 208.115.233.200/298LSN-DLLSTX-1unknown———
└ 208.115.233.208/298LSN-DLLSTX-1unknown———
└ 208.115.233.216/298LSN-DLLSTX-1unknown———
└ 208.115.233.232/298LSN-DLLSTX-1unknown———
└ 208.115.233.240/298LSN-DLLSTX-1unknown———

Composition

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

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Hosting22889%5
VPNanonymizer2811%28

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Mar 2023
Current origin since
Mar 2023 · 3.7 yr
Origin networks
1