Data as of Nov 13, 2026

2.57.169.0/24

Anonymizer · VPN

Orion Network Limited · space held by TnR Technologies B.V.

Announcement
this exact prefix
RPKI valid
Announced by
Type
VPN
IPv4 market

Path

1 · Holder
record created Jul 12, 2021
2 · Leased from
3 · Announced by
AS41564 Orion Network Limited
since Jun 2025 · 16 mo ago
4 · Use
VPN servicesnamed Kape Technologies, ExpressVPN
VPN

Operators, sellers and brokers

VPN services

NameParentIn 2.57.169.0/24/24s
Kape Technologies
25399%
1
ExpressVPNKape Technologies
31.2%
1

Lineage

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

2.57.169.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 2, 2020
    Announced
    AS22923 Netminders Server Hosting
  3. Feb 20, 2020
    Assigned
    VPN Consumer Toronto, Canada
    ASSIGNED PA
    2.57.169.0/24
  4. Feb 20, 2020– Apr 29, 2025
    Announced
    AS7040 Netminders Server Hosting
    Hosting
  5. Jul 12, 2021
    Registry record
    TnR Technologies B.V.
    ALLOCATED PA
    2.57.168.0/22
  6. Jun 29, 2025– today
    Announced
    AS41564 Orion Network Limited
    Hosting
  7. Jul 7, 2025
    Route object
    AS41564 Orion Network Limited
    RIPE route object for AS41564 Orion Network Limited, maintainer PREFIXBROKER-MNT
  8. today
    Leased from
    PrefixBroker
    IP broker
  9. today
    Used
    Kape Technologies
    VPN
  10. 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
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.169.0/24256TORONTO-ON-CA-2-57-169-0VPN Consumer Toronto, Canada (ORG-VCTC1-RIPE) · CAASSIGNED PAFeb 20, 2020abuse-reports@vpnconsumer.com

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
Apr 2019
Current origin since
Jun 2025 · 1.4 yr
Origin networks
4
Last change of origin
Jun 2025
Recorded history

History

Handoffs
3