Data as of Nov 16, 2026

185.48.52.0/22

Anonymizer · Datacenter proxy18 residential-proxy exits · 30 days

Latitude.sh · space held by trafficforce, UAB

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

Residential-proxy exits

Proxy exits
18
1.8% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
16
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

967 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.48.55.0/24010
185.48.52.0/2408

Proxy providers listing exits

  • Ake.net
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • Infatica
  • LemonPrime
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
IPv4 market

Path

1 · Holder
record created Dec 6, 2021
2 · Leased from
its owner, directly
3 · Announced by
AS396356 Latitude.sh
since Feb 2023 · 3.8 yr ago
4 · Use
Datacenter proxy
anonymizer space, operator not named

Operators, sellers and brokers

Leased from

Owners leasing their own space

NameIn 185.48.52.0/22/24s
trafficforce, UAB
1,024100%
4

Lineage

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

185.48.52.0/22

From the registry to its use

  1. Jun 15, 2014– Dec 10, 2021
    Announced
    AS199026 Alconn SRL
  2. Dec 6, 2021
    Registry record
    trafficforce, UAB
    ALLOCATED PA
    185.48.52.0/22
  3. Feb 2, 2023
    Route object
    AS396356 Latitude.sh
    RIPE route object for AS396356 Latitude.sh, maintainer LIR-LT-TRAFFICFORCE-1-MNT
  4. Feb 4, 2023– today
    Announced
    AS396356 Latitude.sh
    Hosting

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.48.52.0/221,024LT-TRAFFICFORCE-20140218trafficforce, UAB (ORG-TU38-RIPE) · LTALLOCATED PADec 6, 2021abuse@trafficforce.lt
└ 185.48.52.0/23512Mexico-internetunknownASSIGNED PAFeb 2, 2023abuse@trafficforce.lt
via LT-TRAFFICFORCE-20140218
└ 185.48.54.0/23512Mexico-internetunknownASSIGNED PAFeb 2, 2023abuse@trafficforce.lt
via LT-TRAFFICFORCE-20140218

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
Reactivated
First seen
Jun 2014
Current origin since
Feb 2023 · 3.8 yr
Origin networks
2
Last change of origin
Feb 2023
Recorded history

History

Handoffs
1