Data as of Nov 19, 2026

94.125.53.0/24

34 residential-proxy exits · 30 days

JSC 'Redcom-lnternet'

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

Residential-proxy exits

Proxy exits
34
13% of its addresses · 30 days
Always-on exits
1
2.9% of its exits
Providers
52
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

5.1K observations

Proxy providers listing exits

  • 9HTTP
  • AETHYN_ELITE
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXORA
  • PROXYLANE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PacketStream
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

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.52.0/23512REDCOM-BB-UNLIM-2REDCOM Broadband Block 2 for flat-rate accessASSIGNED PADec 13, 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