Data as of Nov 18, 2026

94.187.24.0/21

3 residential-proxy exits · 30 days

OGERO

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

Residential-proxy exits

Proxy exits
3
0.15% of its addresses · 30 days
Always-on exits
1
33% of its exits
Spread
2 of 8
/24s with at least one exit
Providers
33
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

771 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
94.187.28.0/2411
94.187.30.0/2402

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • IPFly
  • IPOasis
  • IPRoyal
  • InfiniteProxies
  • Kookey
  • Novada
  • Oxylabs
  • Proxies.fo
  • Proxiware
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalData
  • VitalProxy

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
94.187.0.0/1732,768LB-LIBANTELECOM-20080818OGERO (ORG-LA84-RIPE) · LBALLOCATED PAAug 18, 2008chebaro@ogero.gov.lb
└ 94.187.24.0/212,048OGERONET2nd allocation inetnum4ASSIGNED PADec 16, 2008chebaro@ogero.gov.lb
via LB-LIBANTELECOM-20080818

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
Jan 2009
Current origin since
Jan 2009 · 18 yr
Origin networks
1