LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

77.34.70.0/24

1 residential-proxy exit · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
19
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

227 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • FlashProxy
  • GonzoProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.34.0.0/15
since Apr 2008
AS12332Residential24,318
35 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.70.48/2816POL-BRANCHVTB-NETBRANCH 2558 A JAR of VTB is In VladivostokASSIGNED PAApr 28, 2008abuse@rt.ru
via RU-RTK-20050601
└ 77.34.70.64/2664POL-PPPOE-NET-UNLDynamic Broadband Clients.ASSIGNED PAJul 17, 2012abuse@rt.ru
via RU-RTK-20050601
└ 77.34.70.128/25128POL-PPPOE-NET-UNLDynamic Broadband Clients.ASSIGNED PAJul 17, 2012abuse@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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

77.34.64.0/20

Routing history

Pattern
Stable
First seen
Mar 2010
Current origin since
Mar 2010 · 17 yr
Origin networks
1