Data as of Nov 11, 2026

2.57.170.0/24

Anonymizer · VPN92 residential-proxy exits · 30 days

F.N.S. Holdings Limited · space held by TnR Technologies B.V.

Announcement
this exact prefix
RPKI valid
Announced by
Type
VPN
Risk
75 / 100 · High

Residential-proxy exits

Proxy exits
92
36% of its addresses · 30 days
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

122 observations
IPv4 market

Path

1 · Holder
record created Jul 12, 2021
2 · Leased from
3 · Announced by
AS206092 F.N.S. Holdings Limited
since Feb 2022 · 4.7 yr ago
4 · Use
VPN servicesnamed Kape Technologies
VPN

Operators, sellers and brokers

VPN services

NameParentIn 2.57.170.0/24/24s
Kape Technologies
256100%
1

Lineage

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

2.57.170.0/24

From the registry to its use

  1. Apr 14, 2019– Apr 25, 2019
    Announced
    AS206164 F.N.S. Holdings Limited
    Hosting
  2. Apr 26, 2019– Mar 4, 2022
    Announced
    AS9009 M247 Europe SRL
    Hosting
  3. Jul 12, 2021
    Registry record
    TnR Technologies B.V.
    ALLOCATED PA
    2.57.168.0/22
  4. Feb 21, 2022– today
    Announced
    AS206092 F.N.S. Holdings Limited
    Hosting
  5. Feb 24, 2022
    Assigned
    VPN Consumer Cosenza, Italy
    ASSIGNED PA
    2.57.170.0/24
  6. Feb 24, 2022
    Route object
    AS206092 F.N.S. Holdings Limited
    RIPE route object for AS206092 F.N.S. Holdings Limited, maintainer PREFIXBROKER-MNT
  7. today
    Leased from
    PrefixBroker
    IP broker
  8. today
    Used
    Kape Technologies
    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
2.57.168.0/221,024NL-TNRTECHNOLOGIES-20190319TnR Technologies B.V. (ORG-TTB8-RIPE) · NLALLOCATED PAJul 12, 2021abuse-2-57-168-0-22@tnrtechnologies.nl
└ 2.57.170.0/24256COSENZA-IT-2-57-170-0VPN Consumer Cosenza, Italy (ORG-VCCI2-RIPE) · ITASSIGNED PAFeb 24, 2022abuse-reports@vpnconsumer.com

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
Apr 2019
Current origin since
Feb 2022 · 4.7 yr
Origin networks
3
Last change of origin
Feb 2022
Recorded history

History

Handoffs
2