Data as of Nov 10, 2026

45.141.80.0/22

Anonymizer · ISP proxy3 residential-proxy exits · 30 days

trafficforce, UAB

Announcement
this exact prefix
RPKI valid
Announced by
Type
ISP proxy
Risk
90 / 100 · Critical

Residential-proxy exits

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

Exits seen per day

7 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
45.141.81.0/2402
45.141.80.0/2401

Proxy providers listing exits

  • DataImpulse
  • Proxy4U
IPv4 market

Path

1 · Holder
record created Dec 16, 2021
2 · Leased from
not leased
3 · Announced by
AS133944 trafficforce, UAB
since Feb 2023 · 3.7 yr ago
4 · Use
ISP proxy
anonymizer space, operator not named

Lineage

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

45.141.80.0/22

From the registry to its use

  1. Aug 12, 2019– Dec 22, 2021
    Announced
    AS31480 SilverCom.RU Ltd.
    Business
  2. Dec 16, 2021
    Registry record
    trafficforce, UAB
    ALLOCATED PA
    45.141.80.0/22
  3. Mar 17, 2022– Feb 3, 2023
    Announced
    AS210906 UAB 'Bite Lietuva'
    Hosting
  4. Feb 9, 2023
    Route object
    AS133944 trafficforce, UAB
    RIPE route object for AS133944 trafficforce, UAB, maintainer LIR-LT-TRAFFICFORCE-1-MNT
  5. Feb 16, 2023– today
    Announced
    AS133944 trafficforce, UAB
    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
45.141.80.0/221,024LT-TRAFFICFORCE-20190814trafficforce, UAB (ORG-TU38-RIPE) · LTALLOCATED PADec 16, 2021abuse@trafficforce.lt
└ 45.141.80.0 - 45.141.81.254511Hordees-CloudunknownASSIGNED PAApr 1, 2022abuse@trafficforce.lt
via LT-TRAFFICFORCE-20190814
└ 45.141.82.0 - 45.141.83.254511Hordees-CloudunknownASSIGNED PAApr 1, 2022abuse@trafficforce.lt
via LT-TRAFFICFORCE-20190814

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
Rotating
First seen
Aug 2019
Current origin since
Feb 2023 · 3.7 yr
Origin networks
3
Last change of origin
Feb 2023
Recorded history

History

Handoffs
2