Data as of Nov 22, 2026

188.126.22.0/24

3 residential-proxy exits · 30 days

Nadejda.Net Ltd

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
32
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

3.2K observations

Proxy providers listing exits

  • AETHYN_ELITE
  • AnyIP
  • BirdProxies
  • Byteful
  • DataImpulse
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • HASDATA
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXORA
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • Proxyma
  • SOTAPROXY
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
188.126.0.0/19
since Sep 2016
AS42049Residential154
18 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.20.0/221,024NADEJDA-NETunknownASSIGNED PASep 11, 2023abuse@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.16.0/20

Routing history

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