Data as of Nov 13, 2026

62.176.69.0/24

12 residential-proxy exits · 30 days

Dimitar Vasilev-9 EOOD · space held by Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
12
4.7% of its addresses · 30 days
Always-on exits
1
8.3% of its exits
Providers
42
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

803 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Datarama
  • Decodo
  • Evomi
  • FastProxy
  • FlashProxy
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NSocks
  • Oxylabs
  • PacketStream
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • Webshare
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
62.176.64.0/19
since Mar 2010
AS8866Residential369
72 always on
Vivacom Bulgaria EAD

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
62.176.64.0/1816,384BG-BTC-20000620Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PADec 17, 2001abuse-ip@vivacom.bg
└ 62.176.68.0/23512Passat_LinkPassat Link PLCASSIGNED PAFeb 17, 2010abuse-ip@vivacom.bg
via BG-BTC-20000620

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

62.176.68.0/23

Routing history

Pattern
Rotating
First seen
Apr 2010
Current origin since
Mar 2023 · 3.6 yr
Origin networks
2
Last change of origin
Mar 2023
Recorded history

History

Handoffs
1