Data as of Nov 22, 2026

185.170.108.0/22

Anonymizer · ISP proxy5 residential-proxy exits · 30 days

UAB code200 · space held by trafficforce, UAB

Announcement
this exact prefix
RPKI valid
Announced by
Type
ISP proxy

Residential-proxy exits

Proxy exits
5
0.49% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
2
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

5 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.170.110.0/2402
185.170.111.0/2402
185.170.108.0/2401

Proxy providers listing exits

  • GSocks
  • VantageProxies
IPv4 market

Path

1 · Holder
record created Feb 3, 2022
2 · Leased from
not leased
3 · Announced by
AS209709 UAB code200
since Sep 2019 · 7.2 yr ago
4 · Use
Proxy providersnamed Oxylabs
ISP proxy

Operators, sellers and brokers

Proxy providers

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

Lineage

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

185.170.108.0/22

From the registry to its use

  1. Sep 20, 2016– Nov 18, 2016
    Announced
    AS203912 Orient Finance Bank PJSC
    Business
  2. Nov 19, 2016– Jul 4, 2017
    Announced
    AS48974 Digital Network S.R.L.
  3. Jun 23, 2017– Jul 16, 2017
    Announced
    AS35346 SC ITNS.NET SRL
    Hosting
  4. Dec 8, 2017– Dec 26, 2018
    Announced
    AS49443 Contrust Solutions S.R.L.
  5. Sep 17, 2019– today
    Announced
    AS209709 UAB code200
    Hosting
  6. Feb 3, 2022
    Registry record
    trafficforce, UAB
    ALLOCATED PA
    185.170.108.0/22
  7. Mar 15, 2024
    Route object
    AS209709 UAB code200
    RIPE route object for AS209709 UAB code200, maintainer LIR-LT-TRAFFICFORCE-1-MNT
  8. 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.108.0/221,024LT-TRAFFICFORCE-20160929trafficforce, UAB (ORG-TU38-RIPE) · LTALLOCATED PAFeb 3, 2022abuse@trafficforce.lt
└ 185.170.108.0/23512GB_home1unknownASSIGNED PAApr 12, 2019abuse@trafficforce.lt
via LT-TRAFFICFORCE-20160929
└ 185.170.110.0/23512GB_home2unknownASSIGNED PAApr 12, 2019abuse@trafficforce.lt
via LT-TRAFFICFORCE-20160929

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
Sep 2016
Current origin since
Sep 2019 · 7.2 yr
Origin networks
5
Last change of origin
Sep 2019
Recorded history

History

Handoffs
4