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

91.151.192.0/20

258 residential-proxy exits · 30 days

Resource-M LLC

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

Residential-proxy exits

Proxy exits
258
6.3% of its addresses · 30 days
Always-on exits
9
3.5% of its exits
Spread
6 of 16
/24s with at least one exit
Providers
92
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

33K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
91.151.202.0/24488
91.151.203.0/24283
91.151.197.0/24257
91.151.192.0/24125
91.151.199.0/2404
91.151.195.0/2402

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CROXY
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HPROXY
  • HideProxy
  • IPCola
  • IPFly
  • IPMUSK
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LUMIPROXY
  • LemonPrime
  • LudaxProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PYPROXY
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • RealProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

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
91.151.192.0/204,096RU-RESOURCE-M-20061220Resource-M LLC (ORG-RL428-RIPE) · RUALLOCATED PANov 22, 2019abuse@nodex.ru
└ 91.151.192.0/23512CTLAN-NETSt. Petersburg, RussiaASSIGNED PAJan 18, 2013abuse@nodex.ru
via RU-RESOURCE-M-20061220
└ 91.151.194.0/23512NODEX-NETNODEX Limited (ORG-NL79-RIPE)ASSIGNED PAJan 18, 2013abuse@nodex.ru
└ 91.151.196.0/24256FINFOR-NETINFOR JSC NetworkASSIGNED PAMar 1, 2007abuse@nodex.ru
via RU-RESOURCE-M-20061220
└ 91.151.197.0/24256GTK-NETGTK Ltd (ORG-GL34-RIPE) · RUASSIGNED PAFeb 27, 2007abuse@nodex.ru
└ 91.151.198.0/24256NODEX-NETNODEX Limited (ORG-NL79-RIPE)ASSIGNED PAJan 18, 2013abuse@nodex.ru
└ 91.151.199.0/24256NODEX-NETNODEX LTD, St. Petersburg, RussiaASSIGNED PAApr 1, 2009abuse@nodex.ru
via RU-RESOURCE-M-20061220
└ 91.151.200.0/24256NODEX-NETNODEX LTD, St. Petersburg, RussiaASSIGNED PADec 23, 2011abuse@nodex.ru
via RU-RESOURCE-M-20061220
└ 91.151.201.0/24256NODEX-NETNODEX LTD, St. Petersburg, RussiaASSIGNED PAJan 17, 2013abuse@nodex.ru
via RU-RESOURCE-M-20061220
└ 91.151.202.0/23512NODEX-NETNODEX LTD, St. Petersburg, RussiaASSIGNED PANov 14, 2018abuse@nodex.ru
via RU-RESOURCE-M-20061220
└ 91.151.204.0/221,024GTK-NETGTK Ltd (ORG-GL34-RIPE) · RUASSIGNED PAJan 21, 2013abuse@nodex.ru

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
Dec 2006
Current origin since
Dec 2006 · 20 yr
Origin networks
1