Data as of Nov 13, 2026

62.176.89.0/24

17 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
17
6.6% of its addresses · 30 days
Providers
46
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

2.7K observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • APROXY
  • ASHBURNPROXIES
  • AnyIP
  • BestProxy
  • BirdProxies
  • BlurPath
  • Byteful
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • GloryCloud
  • IPFly
  • IPMUSK
  • Infatica
  • JoyProxy
  • KindProxy
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • PuraRoute
  • RainProxy
  • RapidProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SwiftProxy
  • Thordata
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
62.176.64.0/19
since Mar 2010
AS8866Residential370
74 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.88.0/23512BTC-BROADBAND-NET-41BTC Broadband ServiceASSIGNED PAJul 2, 2015abuse-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.88.0/23

Routing history

Pattern
Stable
First seen
Dec 2006
Current origin since
Jan 2015 · 12 yr
Origin networks
2
Last change of origin
Jan 2015
Recorded history

History

Handoffs
2