Data as of Nov 17, 2026

136.176.223.0/24

Anonymizer · VPN168 residential-proxy exits · 30 days

F.N.S. Holdings Limited · space held by Stichting de Boys

Announcement
this exact prefix
RPKI valid
Announced by
Type
VPN
Recent change
New origin Oct 10, 2026
its first announcement on record

Residential-proxy exits

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

Exits seen per day

2.9K observations
IPv4 market

Path

Announced by AS206092 since Oct 10, 2026 · 5 wk ago
1 · Holder
record created Aug 18, 2026
2 · Leased from
3 · Announced by
AS206092 F.N.S. Holdings Limited
since Oct 10, 2026 · 5 wk ago
4 · Use
VPN servicesnamed Kape Technologies, ExpressVPN
VPN

Operators, sellers and brokers

VPN services

NameParentIn 136.176.223.0/24/24s
Kape Technologies
25098%
1
ExpressVPNKape Technologies
62.3%
1

Lineage

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

136.176.223.0/24

From the registry to its use

  1. Aug 18, 2026
    Registry record
    Stichting de Boys
    LEGACY
    136.176.192.0/19
  2. Oct 10, 2026– today
    Announced
    AS206092 F.N.S. Holdings Limited
    Hosting
  3. Oct 15, 2026
    Assigned
    VPN Consumer Los Angeles, United States
    LEGACY
    136.176.223.0/24
  4. Oct 19, 2026
    Route object
    AS206092 F.N.S. Holdings Limited
    RIPE route object for AS206092 F.N.S. Holdings Limited, maintainer PREFIXBROKER-MNT
  5. today
    Leased from
    PrefixBroker
    IP broker
  6. today
    Used
    Kape Technologies
    VPN
  7. today
    Used
    ExpressVPN
    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
136.176.192.0/198,192SDB-136-176-192-0Stichting de Boys (ORG-SDB12-RIPE) · NLLEGACYAug 18, 2026abuse@panq.nl
└ 136.176.223.0/24256LOS-ANGELES-CA-US-136-176-223-0VPN Consumer Los Angeles, United States (ORG-VCLA1-RIPE) · USLEGACYOct 15, 2026abuse-reports@vpnconsumer.com

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Oct 10, 2026
Current origin since
Oct 10, 2026 · 1 mo
Origin networks
1