Data as of Nov 22, 2026

212.106.44.0/24

60 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
60
23% of its addresses · 30 days
Providers
85
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

3.8K observations

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • AETHYN_ELITE
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BUYPERSONALPROXY
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlashProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonode
  • GhostConnect
  • HASDATA
  • HELODATA
  • HPROXY
  • HideProxy
  • IPFly
  • IPPeak
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LOKIPROXY
  • LUMIPROXY
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYLANE
  • PROXYON
  • PROXYSAVER
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SwiftProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.106.40.0/21
since Aug 2016
AS15468Residential523PJSC Rostelecom
212.106.32.0/20
since Jul 2011
AS15468Residential1,016PJSC Rostelecom
212.106.32.0/19
since Jun 2008
AS15468Residential2,024PJSC Rostelecom

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.106.32.0/198,192RU-RTK-20080523PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAMay 23, 2008abuse@rt.ru
└ 212.106.44.0/23512MACROREGIONAL_CENTEROJSC Rostelecom, Kaluga branchASSIGNED PAMay 28, 2008abuse@rt.ru
via RU-RTK-20080523

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

Summary

Routing history

Pattern
Stable
First seen
Mar 2016
Current origin since
Feb 2017 · 9.8 yr
Origin networks
2
Last change of origin
Feb 2017
Recorded history

History

Handoffs
1