Data as of Nov 22, 2026

92.60.191.0/24

7 residential-proxy exits · 30 days

Load.me sp. z o. o.

Announcement
RPKI valid
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Always-on exits
1
14% of its exits
Providers
34
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

2.5K observations

Proxy providers listing exits

  • 9HTTP
  • AETHYN_ELITE
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • HASDATA
  • Infatica
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
92.60.176.0/20
since Jul 2019
AS1820Internet provider225
33 always on
Load.me sp. z o. o.

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
92.60.176.0/204,096PL-WNET-20071204Load.me sp. z o. o. (ORG-LSZO44-RIPE) · PLALLOCATED PASep 11, 2024abuse@w-net.eu
└ 92.60.190.0/23512UNLIMITEDFIBERUNLIMITEDFIBERASSIGNED PAJan 4, 2011abuse@w-net.eu
via PL-WNET-20071204

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

Covering aggregate above, the prefix's own history below

92.60.190.0/23

Routing history

Pattern
Stable
First seen
Mar 2010
Current origin since
Aug 2021 · 5.2 yr
Origin networks
1