Data as of Nov 11, 2026

91.92.95.0/24

12 residential-proxy exits · 30 days

Netguard LLC

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

Residential-proxy exits

Proxy exits
12
4.7% of its addresses · 30 days
Always-on exits
3
25% of its exits
Providers
55
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

18K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonBright
  • MarsProxies
  • NSocks
  • NodeProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
91.92.92.0/22
since Apr 2017
AS39251Residential22
4 always on
Netguard LLC

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.92.72.0 - 91.92.103.2558,192BG-NETGUARD-20060815Netguard LLC (ORG-NL288-RIPE) · BGALLOCATED PAOct 26, 2016abuse@netguard.bg
└ 91.92.84.0 - 91.92.99.2554,096BG-NETGUARD-20060815NETGUARD users poolASSIGNED PANov 14, 2017abuse@netguard.bg
via BG-NETGUARD-20060815

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
Reactivated
First seen
Sep 2013
Current origin since
Nov 2022 · 4.0 yr
Origin networks
2
Last change of origin
Nov 2022
Recorded history

History

Handoffs
1