LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

212.124.4.0/23

512 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
512
100% of its addresses · 30 days
Always-on exits
143
28% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
43
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

369K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
212.124.4.0/2480255
212.124.5.0/2463255

Proxy providers listing exits

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

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 212.124.0.0/19

212.124.0.0/19

Routing history

Pattern
Stable
First seen
Oct 2018
Current origin since
Oct 2018 · 8.1 yr
Origin networks
1