Data as of Nov 14, 2026

103.47.52.0/22

Anonymizer · Datacenter proxy379 residential-proxy exits · 30 days

Datacamp Limited · 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
379
37% of its addresses · 30 days
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

22K observations
IPv4 market

Path

1 · Holder
record created Aug 15, 2022
2 · Leased from
its owner, directly
3 · Announced by
AS212238 Datacamp Limited
since Apr 2024 · 2.6 yr ago
4 · Use
Datacenter proxy
anonymizer space, operator not named

Operators, sellers and brokers

Leased from

Owners leasing their own space

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

Lineage

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

103.47.52.0/22

From the registry to its use

  1. Oct 26, 2016– Nov 18, 2016
    Announced
    AS134015 Datanet Hosting Solutions Pvt. Ltd.
  2. Nov 7, 2016– Jul 28, 2017
    Announced
    AS55470 Cyfuture India Pvt. Ltd.
    Hosting
  3. Aug 15, 2022
    Registry record
    trafficforce, UAB
    ALLOCATED PA
    103.47.52.0/22
  4. Oct 31, 2022– Feb 22, 2024
    Announced
    AS212238 Datacamp Limited
    Hosting
  5. Apr 10, 2024
    Route object
    AS212238 Datacamp Limited
    RIPE route object for AS212238 Datacamp Limited, maintainer LIR-LT-TRAFFICFORCE-1-MNT
  6. Apr 11, 2024– today
    Announced
    AS212238 Datacamp Limited
    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
103.47.52.0/221,024LT-TRAFFICFORCE-20141224trafficforce, UAB (ORG-TU38-RIPE) · LTALLOCATED PAAug 15, 2022abuse@trafficforce.lt
└ 103.47.52.0 - 103.47.55.2541,023Angeles3unknownASSIGNED PASep 28, 2022abuse@trafficforce.lt
via LT-TRAFFICFORCE-20141224

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
Oct 2016
Current origin since
Apr 2024 · 2.6 yr
Origin networks
3
Last change of origin
Oct 2022
Recorded history

History

Handoffs
2