Data as of Nov 10, 2026

2.57.176.0/22

Anonymizer · Datacenter proxy

HostRoyale Technologies Pvt Ltd · space held by UAB Linama

Announcement
this exact prefix
RPKI valid
Announced by
Type
Datacenter proxy
Risk
85 / 100 · Critical
IPv4 market

Path

1 · Holder
record created Mar 22, 2021
2 · Leased from
its owner, directly
3 · Announced by
AS203020 HostRoyale Technologies Pvt Ltd
since May 2020 · 6.5 yr ago
4 · Use
Proxy providersnamed Oxylabs
Datacenter proxy

Operators, sellers and brokers

Proxy providers

NameParentIn 2.57.176.0/22/24s
OxylabsTesonet
1,024100%
4
Leased from

Owners leasing their own space

NameIn 2.57.176.0/22/24s
UAB Linama
1,024100%
4

Lineage

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

2.57.176.0/22

From the registry to its use

  1. Apr 14, 2019– Jun 24, 2019
    Announced
    AS47987 Zemlyaniy Dmitro Leonidovich
    Hosting
  2. Jul 7, 2019– Jan 14, 2020
    Announced
    AS12679 Sokolov Dmitry Nikolaevich
  3. Jan 15, 2020– May 13, 2020
    Announced
    AS51765 Oy Crea Nova Hosting Solution Ltd
    Hosting
  4. May 2, 2020– today
    Announced
    AS203020 HostRoyale Technologies Pvt Ltd
    Hosting
  5. May 8, 2020
    Route object
    AS203020 HostRoyale Technologies Pvt Ltd
    RIPE route object for AS203020 HostRoyale Technologies Pvt Ltd, maintainer MNT-HASHPOWER
  6. Mar 22, 2021
    Registry record
    UAB Linama
    ALLOCATED PA
    2.57.176.0/22
  7. today
    Used
    Oxylabs
    Proxy seller

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.176.0/221,024LT-LINAMA-20190320UAB Linama (ORG-UL208-RIPE) · LTALLOCATED PAMar 22, 2021abuse@ip4telcom.com
└ 2.57.176.0/23512DCunknownASSIGNED PAFeb 2, 2021abuse@ip4telcom.com
via LT-LINAMA-20190320
└ 2.57.178.0/23512DC01unknownASSIGNED PAFeb 2, 2021abuse@ip4telcom.com
via LT-LINAMA-20190320

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
Apr 2019
Current origin since
May 2020 · 6.5 yr
Origin networks
4
Last change of origin
May 2020
Recorded history

History

Handoffs
3