Data as of Nov 17, 2026

212.220.71.0/24

8 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
1
13% of its exits
Providers
37
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

1.6K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • IPROCKET_PREMIUM
  • Infatica
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.220.0.0/16
since Sep 2018
AS12389Residential3,700
69 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.220.0.0/1665,536RU-RTK-980311PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAApr 17, 2002abuse@rt.ru
└ 212.220.71.0/24256USIWI-FI ChkalovskyASSIGNED PAJan 20, 2011abuse@rt.ru
via RU-RTK-980311

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.220.64.0/18

Routing history

Pattern
Stable
First seen
Nov 2005
Current origin since
Nov 2017 · 9.0 yr
Origin networks
2
Last change of origin
Nov 2017
Recorded history

History

Handoffs
1