Data as of Nov 14, 2026

91.186.32.0/19

107 residential-proxy exits · 30 days

Wobcom GmbH

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

Residential-proxy exits

Proxy exits
107
1.3% of its addresses · 30 days
Spread
16 of 32
/24s with at least one exit
Providers
48
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

17K observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • Byteful
  • DataImpulse
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FloppyData
  • GSocks
  • GhostConnect
  • GoProxies
  • IPFly
  • IPMUSK
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYON
  • Proxiware
  • Proxmint
  • Proxy4U
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE

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.186.32.0/198,192DE-WOBCOM-20061107Wobcom GmbH (ORG-WG5-RIPE) · DEALLOCATED PANov 7, 2006abuse@wobcom.de
└ 91.186.32.0 - 91.186.40.2552,304WOBCOM-NETWobcom Dynamic PoolASSIGNED PANov 17, 2006abuse@wobcom.de
via DE-WOBCOM-20061107
└ 91.186.41.0 - 91.186.46.2551,536WOBCOM-NETWobcom Dynamic PoolASSIGNED PAJun 8, 2007abuse@wobcom.de
via DE-WOBCOM-20061107
└ 91.186.47.0 - 91.186.55.2552,304WOBCOM-NETWobcom Dynamic PoolASSIGNED PANov 17, 2006abuse@wobcom.de
via DE-WOBCOM-20061107
└ 91.186.56.0/212,048WOBCOM-NETWobcom Dynamic PoolASSIGNED PADec 12, 2007abuse@wobcom.de
via DE-WOBCOM-20061107

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

Who has announced this prefix

Summary

Routing history

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