Data as of Nov 19, 2026

212.122.7.0/24

3 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
3
100% of its exits
Providers
29
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

9.0K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • MarsProxies
  • NSocks
  • NodeMaven
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • Shifter
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.122.0.0/20
since May 2005
AS12332Residential5
3 always on
PJSC Rostelecom
212.122.0.0/19
since May 2005
AS12332Residential116
3 always on
PJSC 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.122.0.0/198,192RU-RTK-981026PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 9, 2001abuse@rt.ru
└ 212.122.7.0 - 212.122.9.255768POL-PPPOE-NET-UNLDynamic Broadband Clients.ASSIGNED PAJul 17, 2012abuse@rt.ru
via RU-RTK-981026

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
Nov 2019
Current origin since
Nov 2019 · 7.0 yr
Origin networks
1