Data as of Nov 11, 2026

178.211.97.0/24

5 residential-proxy exits · 30 days

ADAMANT, Ltd.

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
3
60% of its exits
Providers
30
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

5.5K observations

Proxy providers listing exits

  • 2Captcha
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • GoProxies
  • GonzoProxy
  • IPOasis
  • Infatica
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.211.96.0/19
since Aug 2010
AS8788Residential120
17 always on
ADAMANT, Ltd.

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.211.96.0/198,192UA-ADAM-20100715ADAMANT, Ltd. (ORG-AC6-RIPE) · UAALLOCATED PAJul 15, 2010abuse@adamant.ua
└ 178.211.96.0/212,048ADAMANT-BROADBAND3Adamant Home NetworkASSIGNED PAJul 15, 2010abuse@adamant.ua
via UA-ADAM-20100715

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

178.211.96.0/20

Routing history

Pattern
Stable
First seen
May 2025
Current origin since
May 2026 · 6 mo
Origin networks
1