Data as of Nov 10, 2026

45.82.232.0/22

41 residential-proxy exits · 30 days

Martin Fryzl

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

Residential-proxy exits

Proxy exits
41
4.0% of its addresses · 30 days
Always-on exits
4
9.8% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
53
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

7.6K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
45.82.234.0/24318
45.82.235.0/24117
45.82.233.0/2406

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BartProxies
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • 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
45.82.232.0/221,024CZ-FRYZL-20190527Martin Fryzl (ORG-MF143-RIPE) · CZALLOCATED PAMay 27, 2019martin@fryzl.net
└ 45.82.232.0/24256FryzlNet-232unknownASSIGNED PANov 4, 2019martin@fryzl.net
via CZ-FRYZL-20190527
└ 45.82.233.0/24256FryzlNet-233unknownASSIGNED PANov 4, 2019martin@fryzl.net
via CZ-FRYZL-20190527
└ 45.82.234.0/23512FryzlNet-234-235unknownASSIGNED PANov 4, 2019martin@fryzl.net
via CZ-FRYZL-20190527

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
Oct 2019
Current origin since
Oct 2019 · 7.1 yr
Origin networks
1