Data as of Nov 13, 2026

212.124.7.0/24

256 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
256
100% of its addresses · 30 days
Always-on exits
48
19% of its exits
Providers
47
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

160K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CoreProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • MangoProxy
  • MarsProxies
  • Maskify
  • NSocks
  • Novada
  • Oxylabs
  • PacketStream
  • PrivateProxy
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • RolaProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.124.0.0/19
since Oct 2018
AS12389Residential2,064
571 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.124.0.0/198,192RU-RTK-20080529PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAMay 29, 2008abuse@rt.ru
└ 212.124.0.0/212,048MACROREGIONAL_CENTEROJSC Rostelecom, Ivanovo branchASSIGNED PAMar 15, 2013abuse@rt.ru
via RU-RTK-20080529

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

212.124.6.0/23

Routing history

Pattern
Stable
First seen
Apr 2019
Current origin since
Apr 2019 · 7.6 yr
Origin networks
1