Data as of Nov 14, 2026

77.40.62.0/24

248 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
248
97% of its addresses · 30 days
Always-on exits
178
72% of its exits
Providers
38
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

292K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CoreProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • Maskify
  • NSocks
  • Oxylabs
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.40.0.0/17
since Mar 2016
AS12389Residential5,138
454 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
77.40.0.0/1732,768RU-RTK-20061120PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 20, 2006abuse@rt.ru
└ 77.40.8.0 - 77.40.79.25518,432MARI-VOLGATELECOMxDSL dynamic poolsASSIGNED PADec 17, 2024abuse@rt.ru
via RU-RTK-20061120

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
Feb 2012
Current origin since
Apr 2017 · 9.6 yr
Origin networks
3
Last change of origin
Aug 2016
Recorded history

History

Handoffs
2