Data as of Nov 17, 2026

188.126.4.0/24

17 residential-proxy exits · 30 days

Nadejda.Net Ltd

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

Residential-proxy exits

Proxy exits
17
6.6% of its addresses · 30 days
Always-on exits
2
12% of its exits
Providers
46
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

4.7K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • Geonode
  • GonzoProxy
  • IPOasis
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • Kookey
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Shifter
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
188.126.0.0/19
since Sep 2016
AS42049Residential151
17 always on
Nadejda.Net Ltd

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
188.126.0.0/198,192BG-NADEJDANET-20090722Nadejda.Net Ltd (ORG-NL125-RIPE) · BGALLOCATED PAJul 22, 2009abuse@datalink.bg
└ 188.126.4.0/221,024NADEJDA-NETNadejdaNet LtdASSIGNED PAAug 31, 2011abuse@datalink.bg
via BG-NADEJDANET-20090722

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

188.126.0.0/20

Routing history

Pattern
Stable
First seen
Aug 2009
Current origin since
Sep 2016 · 10 yr
Origin networks
1