Data as of Nov 17, 2026

37.79.219.0/24

5 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
4
80% of its exits
Providers
34
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

8.7K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • MangoProxy
  • NodeMaven
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.79.208.0/20
since Nov 2017
AS12389Residential35
9 always on
PJSC Rostelecom
via Dynamic distribution IP's for broadband services
37.78.0.0/15
since Oct 2018
AS12389Residential39,262
38 always on
PJSC Rostelecom

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
37.78.0.0/15131,072RU-RTK-20120131PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJan 31, 2012abuse@rt.ru
└ 37.79.0.0/1665,536USI_ADSL_USERSDynamic distribution IP's for broadband servicesSUB-ALLOCATED PAJan 29, 2016abuse@rt.ru
via RU-RTK-20120131

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

37.79.216.0/22

Routing history

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

History

Handoffs
1