Data as of Nov 13, 2026

93.91.240.0/22

11 residential-proxy exits · 30 days

Core4Net, s.r.o.

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

Residential-proxy exits

Proxy exits
11
1.1% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
42
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

744 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
93.91.243.0/2406
93.91.241.0/2404

Proxy providers listing exits

  • 2Captcha
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GonzoProxy
  • HideProxy
  • IPOasis
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • ProxiesVision
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
93.91.240.0/20
since Sep 2008
AS47269Residential30
4 always on
Core4Net, s.r.o.

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
93.91.240.0/204,096CZ-CORE4NET-20080521Core4Net, s.r.o. (ORG-CS455-RIPE) · CZALLOCATED PAMay 21, 2008abuse@core4net.cz
└ 93.91.240.0/24256Infrastructure_and_data_centerunknownSUB-ALLOCATED PAOct 3, 2016abuse@core4net.cz
via CZ-CORE4NET-20080521
└ 93.91.242.0/24256clients_optical_networkunknownSUB-ALLOCATED PAOct 3, 2016abuse@core4net.cz
via CZ-CORE4NET-20080521
└ 93.91.243.0/24256NAT_wifi_networkunknownSUB-ALLOCATED PAOct 3, 2016abuse@core4net.cz
via CZ-CORE4NET-20080521

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jan 2015
Current origin since
Aug 2016 · 10 yr
Origin networks
1