Data as of Nov 22, 2026

31.47.139.0/24

10 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
10
3.9% of its addresses · 30 days
Providers
48
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

1.0K observations

Proxy providers listing exits

  • AETHYN_BASIC
  • AETHYN_ELITE
  • Ake.net
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • DataImpulse
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • GEEKPROXY_TURBO
  • GSocks
  • GloryCloud
  • IPFly
  • IPMUSK
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • KindProxy
  • Kookey
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • SwiftProxy
  • VantageProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
31.47.128.0/198,192RU-RTK-20110322PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAApr 25, 2022abuse@rt.ru
└ 31.47.128.0/204,096TVINGOTotal-Net LtdASSIGNED PAOct 16, 2024abuse@rt.ru
via RU-RTK-20110322

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 31.47.128.0/20

31.47.128.0/20

Routing history

Pattern
Reactivated
First seen
Apr 2011
Current origin since
Oct 2024 · 2.1 yr
Origin networks
2
Last change of origin
Oct 2024
Recorded history

History

Handoffs
1