Data as of Nov 13, 2026

37.76.167.0/24

60 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
60
23% of its addresses · 30 days
Providers
75
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

3.7K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HELODATA
  • HideProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.76.160.0/19
since May 2012
AS13056Residential2,291PJSC Rostelecom
37.76.128.0/18
since Oct 2018
AS12389Residential7,514PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
37.76.128.0/1816,384RU-RTK-20120131PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJan 31, 2012abuse@rt.ru
└ 37.76.160.0/198,192MACROREGIONAL_CENTEROJSC Rostelecom, Tambov branchASSIGNED PAApr 27, 2012abuse@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

RPKI

Route origin authorizations

ROA prefixASNMax lenAnchorVerdict
37.76.160.0/20AS12389/20RIPERPKI valid
37.76.160.0/19AS13056/19RIPEAnother network
37.76.128.0/18AS12389/18RIPEToo specific
IRR

Route objects on 37.76.160.0/20

OriginRegistryDescriptionMaintainerModified
AS12389 RIPERostelecom networksROSTELECOM-MNTOct 25, 2018