Data as of Nov 14, 2026

185.99.28.0/22

Anonymizer · ISP proxy2 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
2
0.20% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
1
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

2 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.99.28.0/2401
185.99.29.0/2401

Proxy providers listing exits

  • GSocks
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.99.28.0/22/24s
OxylabsTesonet
1,024100%
4

Lineage

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

185.99.28.0/22

From the registry to its use

  1. May 8, 2015– Aug 15, 2015
    Announced
    AS29632 Netassist International EOOD
  2. Aug 22, 2015– Jun 27, 2016
    Announced
  3. Aug 27, 2016– Apr 13, 2019
    Announced
  4. Sep 17, 2019– today
    Announced
    AS209709 UAB code200
    Hosting
  5. Feb 3, 2022
    Registry record
    trafficforce, UAB
    ALLOCATED PA
    185.99.28.0/22
  6. Mar 15, 2024
    Route object
    AS209709 UAB code200
    RIPE route object for AS209709 UAB code200, maintainer LIR-LT-TRAFFICFORCE-1-MNT
  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
185.99.28.0/221,024LT-TRAFFICFORCE-20150506trafficforce, UAB (ORG-TU38-RIPE) · LTALLOCATED PAFeb 3, 2022abuse@trafficforce.lt
└ 185.99.28.0/23512TF-GB-FiberunknownASSIGNED PAFeb 4, 2022abuse@trafficforce.lt
via LT-TRAFFICFORCE-20150506
└ 185.99.30.0/23512TF-GB-Fiber2unknownASSIGNED PAFeb 4, 2022abuse@trafficforce.lt
via LT-TRAFFICFORCE-20150506

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

History

Handoffs
2