Data as of Nov 16, 2026

194.126.136.0/22

258 residential-proxy exits · 30 days

IncoNet Data Management sal

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

Residential-proxy exits

Proxy exits
258
25% of its addresses · 30 days
Always-on exits
215
83% of its exits
Spread
2 of 4
/24s with at least one exit
Providers
37
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

158K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
194.126.137.0/24215254
194.126.138.0/2404

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • Kookey
  • MangoProxy
  • Maskify
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PacketStream
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
194.126.136.0/212,048LB-INCONET-970307IncoNet Data Management sal (ORG-IA38-RIPE) · LBALLOCATED PA—nocbix@idm.net.lb
└ 194.126.136.0/221,024LB-IDMIDMASSIGNED PAFeb 13, 2008nocbix@idm.net.lb
via LB-INCONET-970307

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 194.126.136.0/21

194.126.136.0/21

Routing history

Pattern
Stable
First seen
Mar 2008
Current origin since
Mar 2008 · 19 yr
Origin networks
1