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

77.37.138.0/24

8 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
5
63% of its exits
Providers
38
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

2.8K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyWing
  • Proxyma
  • Shifter
  • Thordata
  • VitalData
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
77.37.128.0/1732,768RU-RTK-20070321PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAMar 21, 2007abuse@rt.ru
└ 77.37.128.0/198,192NCN-INFRANCNETASSIGNED PAJul 27, 2026abuse@rt.ru
via RU-RTK-20070321

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

Who has announced 77.37.128.0/17

77.37.128.0/17

Routing history

Pattern
Stable
First seen
May 2007
Current origin since
May 2007 · 20 yr
Origin networks
1