Data as of Nov 10, 2026

92.37.136.0/22

273 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
273
27% of its addresses · 30 days
Always-on exits
2
0.73% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
78
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

21K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
92.37.139.0/24275
92.37.136.0/24070
92.37.137.0/24070
92.37.138.0/24059

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPCola
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • Maskify
  • NSocks
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • TalorData
  • VantageProxies
  • VitalData
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
92.37.128.0/18
since Feb 2008
AS34584Residential4,414
495 always on
PJSC Rostelecom
92.37.128.0/17
since Feb 2008
AS34584Residential8,343
539 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
92.37.128.0/1732,768RU-RTK-20080118PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJan 18, 2008abuse@rt.ru
└ 92.37.136.0/221,024KHT-XDSLPPPoE xDSL links in Khabarovsk city, ATS-30 nodeASSIGNED PANov 18, 2008abuse@rt.ru
via RU-RTK-20080118

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
Apr 2010
Current origin since
Feb 2015 · 12 yr
Origin networks
2
Last change of origin
Feb 2015
Recorded history

History

Handoffs
1