Data as of Nov 16, 2026

62.176.104.0/22

4 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
4
0.39% of its addresses · 30 days
Always-on exits
1
25% of its exits
Spread
2 of 4
/24s with at least one exit
Providers
24
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

273 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
62.176.104.0/2413
62.176.105.0/2401

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • DataImpulse
  • FastProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • IPRoyal
  • KocerRoxy
  • Kookey
  • LemonBright
  • NextProxy
  • Novada
  • Proxy4U
  • ProxyRack
  • ProxyWing
  • TalorData
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
62.176.104.0/21
since May 2024
AS8866Residential130
31 always on
Vivacom Bulgaria EAD

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, 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.104.0/221,024BTC-LANBTC-LAN customersASSIGNED PAApr 20, 2012abuse-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

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Jul 2019 · 7.3 yr
Origin networks
2
Last change of origin
Aug 2011
Recorded history

History

Handoffs
1