Data as of Nov 12, 2026

185.22.136.0/22

15 residential-proxy exits · 30 days

PHU AMPLUS Krzysztof Jonski

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

Residential-proxy exits

Proxy exits
15
1.5% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
41
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

717 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.22.136.0/2409
185.22.138.0/2406

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • GonzoProxy
  • IPPeak
  • Infatica
  • Kookey
  • LemonBright
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VitalExclusive

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
185.22.136.0/221,024PL-AMPLUS-20130329PHU AMPLUS Krzysztof Jonski (ORG-PAKJ1-RIPE) · PLALLOCATED PAMar 28, 2013abuse@amplus.net.pl
└ 185.22.136.0/24256AMPLUSNETunknownASSIGNED PAJan 27, 2014abuse@amplus.net.pl
via PL-AMPLUS-20130329
└ 185.22.137.0/24256AMPLUSNETPHU AMPLUS Krzysztof Jonski (ORG-PAKJ1-RIPE) · PLASSIGNED PAJan 27, 2014abuse@amplus.net.pl
└ 185.22.138.0/24256AMPLUSNETPHU AMPLUS Krzysztof Jonski (ORG-PAKJ1-RIPE) · PLASSIGNED PAJan 27, 2014abuse@amplus.net.pl
└ 185.22.139.0/24256AMPLUSNETPHU AMPLUS Krzysztof Jonski (ORG-PAKJ1-RIPE) · PLASSIGNED PAJan 27, 2014abuse@amplus.net.pl

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
Aug 2013
Current origin since
Aug 2013 · 13 yr
Origin networks
1