Data as of Nov 21, 2026

185.170.252.0/22

Anonymizer · Datacenter proxy1 residential-proxy exit · 30 days

UAB code200

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

Residential-proxy exits

Proxy exits
1
0.10% of its addresses · 30 days
Spread
1 of 4
/24s with at least one exit
Providers
1
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

1 observation

Proxy providers listing exits

  • VantageProxies
IPv4 market

Path

1 · Holder
record created Jul 2, 2020
2 · Leased from
not leased
3 · Announced by
AS205964 UAB code200
since Mar 2018 · 8.7 yr ago
4 · Use
Proxy providersnamed Oxylabs
Datacenter proxy

Operators, sellers and brokers

Proxy providers

NameParentIn 185.170.252.0/22/24s
OxylabsTesonet
1,024100%
4

Lineage

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

185.170.252.0/22

From the registry to its use

  1. Mar 2, 2018– today
    Announced
    AS205964 UAB code200
    Hosting
  2. Jul 2, 2020
    Registry record
    UAB code200
    ALLOCATED PA
    185.170.252.0/22
  3. 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
185.170.252.0/221,024LT-CODE200-20161003UAB code200 (ORG-UC48-RIPE) · LTALLOCATED PAJul 2, 2020abuse@code200.global
└ 185.170.252.0/23512LT_InternetunknownASSIGNED PASep 26, 2018abuse@code200.global
via LT-CODE200-20161003
└ 185.170.254.0/23512LT_CloudunknownASSIGNED PASep 26, 2018abuse@code200.global
via LT-CODE200-20161003

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
Mar 2018
Current origin since
Mar 2018 · 8.7 yr
Origin networks
1