Data as of Nov 19, 2026

77.34.10.224/28

No anonymizer space · no proxy exits in 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
12
75% of its addresses · listed by providers
Providers
43
selling exits here

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BUYPERSONALPROXY
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.34.0.0/20
since Mar 2010
AS12332Residential78
7 always on
PJSC Rostelecom
77.34.0.0/15
since Apr 2008
AS12332Residential23,859
42 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
77.34.0.0/15131,072RU-RTK-20050601PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJan 24, 2007abuse@rt.ru
└ 77.34.10.224/2816POL-SBERNABK8635-NETSberBank 8635ASSIGNED PAJul 26, 2011abuse@rt.ru
via RU-RTK-20050601

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

77.34.10.0/24

Routing history

Pattern
Stable
First seen
Nov 2019
Current origin since
Nov 2019 · 7.0 yr
Origin networks
1