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

185.243.172.0/22

15 residential-proxy exits · 30 days

Jiri Tlapak

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

Residential-proxy exits

Proxy exits
15
1.5% of its addresses · 30 days
Always-on exits
1
6.7% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
40
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

2.8K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.243.172.0/2417
185.243.174.0/2404
185.243.175.0/2404

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • GSocks
  • GeekProxy
  • Geonix
  • GonzoProxy
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • 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
185.243.172.0/221,024CZ-JIRITLAPAK-20180129Jiri Tlapak (ORG-JT76-RIPE) · CZALLOCATED PAJan 29, 2018zneuziti@tlapnet.cz
└ 185.243.172.0/24256Tlapnet-CZunknownASSIGNED PAAug 17, 2026zneuziti@tlapnet.cz
via CZ-JIRITLAPAK-20180129
└ 185.243.173.0/24256Tlapnet-CZunknownASSIGNED PAAug 17, 2026zneuziti@tlapnet.cz
via CZ-JIRITLAPAK-20180129
└ 185.243.174.0/24256Tlapnet-CZunknownASSIGNED PAAug 17, 2026zneuziti@tlapnet.cz
via CZ-JIRITLAPAK-20180129
└ 185.243.175.0/24256Tlapnet-CZunknownASSIGNED PAAug 17, 2026zneuziti@tlapnet.cz
via CZ-JIRITLAPAK-20180129

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
Rotating
First seen
Jul 2018
Current origin since
May 2025 · 1.5 yr
Origin networks
2
Last change of origin
May 2025
Recorded history

History

Handoffs
1