Data as of Nov 21, 2026

94.125.55.0/24

32 residential-proxy exits · 30 days

JSC 'Redcom-lnternet'

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

Residential-proxy exits

Proxy exits
32
13% of its addresses · 30 days
Providers
40
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

896 observations

Proxy providers listing exits

  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • IPFly
  • IPMUSK
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • LUMIPROXY
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXORA
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
94.125.48.0/212,048RU-REDCOM-20080818JSC "Redcom-lnternet" (ORG-RA23-RIPE) · RUALLOCATED PAAug 20, 2008abuse@redcom.ru
└ 94.125.54.0/23512REDCOM-BB-UNLIM-3REDCOM Broadband Block 3 for flat-rate accessASSIGNED PAFeb 11, 2010abuse@redcom.ru
via RU-REDCOM-20080818

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 94.125.48.0/21

94.125.48.0/21

Routing history

Pattern
Stable
First seen
Aug 2008
Current origin since
Aug 2008 · 18 yr
Origin networks
1