Data as of Nov 14, 2026

64.31.27.0/24

Anonymizer · VPN31 residential-proxy exits · 30 days

Limestone Networks, Inc.

Announcement
this exact prefix
RPKI valid
Announced by
Type
VPN

Residential-proxy exits

Proxy exits
31
12% of its addresses · 30 days
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

202 observations
IPv4 market

Path

1 · Holder
record created Dec 27, 2010
2 · Leased from
not leased
3 · Announced by
AS46475 Limestone Networks, Inc.
since Dec 2024 · 23 mo ago
4 · Use
VPN servicesnamed TunnelBear
VPN

Operators, sellers and brokers

VPN services

NameParentIn 64.31.27.0/24/24s
TunnelBearMcAfee
256100%
1

Lineage

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

64.31.27.0/24

From the registry to its use

  1. Dec 27, 2010
    Registry record
    Limestone Networks, Inc.
    Direct Allocation
    64.31.0.0/18
  2. Jan 8, 2011– today
    Announced
    AS46475 Limestone Networks, Inc.
    as part of 64.31.0.0/18
    64.31.0.0/18
  3. Dec 7, 2024– today
    Announced
    AS46475 Limestone Networks, Inc.
    Hosting
  4. today
    Used
    TunnelBear
    VPN

Announcements

Less specific

Covering announcements

PrefixOriginTypeHolderRPKI
64.31.0.0/18
since Jan 2011
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
64.31.0.0/1816,384LIMESTONE-NETWORKSLimestone Networks, Inc. (LIMES-2) · USDirect AllocationDec 27, 2010abuse@limestonenetworks.com
└ 64.31.27.192/312LSN-DLLSTX-1unknownReassignedOct 7, 2025abuse@limestonenetworks.com
via LIMESTONE-NETWORKS
└ 64.31.27.194/312LSN-DLLSTX-1unknownReassignedDec 14, 2025abuse@limestonenetworks.com
via LIMESTONE-NETWORKS
└ 64.31.27.196/304LSN-DLLSTX-1unknownReassignedDec 18, 2025abuse@limestonenetworks.com
via LIMESTONE-NETWORKS
└ 64.31.27.200/312LSN-DLLSTX-1unknownReassignedApr 10, 2025abuse@limestonenetworks.com
via LIMESTONE-NETWORKS
└ 64.31.27.202/312LSN-DLLSTX-1unknownReassignedApr 23, 2025abuse@limestonenetworks.com
via LIMESTONE-NETWORKS
└ 64.31.27.206/312LSN-DLLSTX-1unknownReassignedJan 6, 2026abuse@limestonenetworks.com
via LIMESTONE-NETWORKS
└ 64.31.27.210/312LSN-DLLSTX-1unknownReassignedAug 22, 2026abuse@limestonenetworks.com
via LIMESTONE-NETWORKS
└ 64.31.27.212/312LSN-DLLSTX-1unknownReassignedOct 29, 2025abuse@limestonenetworks.com
via LIMESTONE-NETWORKS
└ 64.31.27.214/312LSN-DLLSTX-1unknownReassignedNov 4, 2025abuse@limestonenetworks.com
via LIMESTONE-NETWORKS
└ 64.31.27.224/312LSN-DLLSTX-1unknownReassignedApr 23, 2025abuse@limestonenetworks.com
via LIMESTONE-NETWORKS
└ 64.31.27.226/312LSN-DLLSTX-1unknownReassignedMay 13, 2025abuse@limestonenetworks.com
via LIMESTONE-NETWORKS
└ 64.31.27.228/304LSN-DLLSTX-1unknownReassignedJan 24, 2026abuse@limestonenetworks.com
via LIMESTONE-NETWORKS
└ 64.31.27.232/312LSN-DLLSTX-1unknownReassignedMar 3, 2025abuse@limestonenetworks.com
via LIMESTONE-NETWORKS
└ 64.31.27.236/312LSN-DLLSTX-1unknownReassignedJul 8, 2026abuse@limestonenetworks.com
via LIMESTONE-NETWORKS
└ 64.31.27.238/312LSN-DLLSTX-1unknownReassignedMar 18, 2025abuse@limestonenetworks.com
via LIMESTONE-NETWORKS
└ 64.31.27.240/304LSN-DLLSTX-1unknownReassignedMay 3, 2025abuse@limestonenetworks.com
via LIMESTONE-NETWORKS
└ 64.31.27.246/312LSN-DLLSTX-1unknownReassignedSep 28, 2026abuse@limestonenetworks.com
via LIMESTONE-NETWORKS
└ 64.31.27.250/312LSN-DLLSTX-1unknownReassignedApr 21, 2026abuse@limestonenetworks.com
via LIMESTONE-NETWORKS
└ 64.31.27.252/312LSN-DLLSTX-1unknownReassignedJan 8, 2026abuse@limestonenetworks.com
via LIMESTONE-NETWORKS

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
Dec 2024
Current origin since
Dec 2024 · 1.9 yr
Origin networks
1