Data as of Nov 20, 2026

31.6.11.0/24

Anonymizer · VPN19 residential-proxy exits · 30 days

Powerhouse Management, Inc. · space held by Xspeedient, LLC

Announcement
this exact prefix
RPKI valid
Announced by
Type
VPN

Residential-proxy exits

Proxy exits
19
7.4% of its addresses · 30 days
Providers
22
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

2.4K observations

Proxy providers listing exits

  • 9HTTP
  • Ake.net
  • BirdProxies
  • ByteProxies
  • DataImpulse
  • GeekProxy
  • GonzoProxy
  • IPCola
  • Infatica
  • NodeProxy
  • PSBProxy
  • PrivateByte
  • Proxies.fo
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • Proxyma
  • Q2IP
  • RainProxy
  • Shifter
  • Smartproxy
  • VitalExclusive
IPv4 market

Path

1 · Holder
record created Sep 13, 2023
2 · Leased from
not leased
3 · Announced by
AS22363 Powerhouse Management, Inc.
since Nov 2014 · 12.0 yr ago
4 · Use
VPN servicesnamed VyprVPN
VPN

Operators, sellers and brokers

VPN services

NameParentIn 31.6.11.0/24/24s
VyprVPNGolden Frog
256100%
1

Lineage

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

31.6.11.0/24

From the registry to its use

  1. Oct 21, 2011
    Assigned
    GR Dynamic IPs
    ASSIGNED PA
    31.6.11.0/24
  2. Nov 6, 2014
    Route object
    AS22363 Powerhouse Management, Inc.
    RADB route object for AS22363 Powerhouse Management, Inc., maintainer MAINT-AS30094
  3. Nov 15, 2014– today
    Announced
    AS22363 Powerhouse Management, Inc.
    Hosting
  4. Sep 13, 2023
    Registry record
    Xspeedient, LLC
    ALLOCATED PA
    31.6.0.0/18
  5. today
    Used
    VyprVPN
    VPN

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
31.6.0.0/1816,384US-XSPEEDIENT-20110408Xspeedient, LLC (ORG-XL27-RIPE) · USALLOCATED PASep 13, 2023dmca@xspeedient.net
└ 31.6.11.0/24256YHC-NET-CUST-4GR Dynamic IPsASSIGNED PAOct 21, 2011dmca@xspeedient.net
via US-XSPEEDIENT-20110408

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Nov 2014
Current origin since
Nov 2014 · 12 yr
Origin networks
1