Data as of Nov 18, 2026

212.220.72.0/21

1 residential-proxy exit · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
1
0.05% of its addresses · 30 days
Spread
1 of 8
/24s with at least one exit
Providers
20
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

189 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.220.0.0/16
since Sep 2018
AS12389Residential3,715
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.72.0/212,048USI_ADSL_USERSDynamic distribution IP's for broadband servicesASSIGNED PAMay 26, 2008abuse@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