Data as of Nov 16, 2026

212.50.77.0/24

6 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
6
2.3% of its addresses · 30 days
Always-on exits
1
17% of its exits
Providers
38
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

1.4K observations

Proxy providers listing exits

  • 2Captcha
  • 9HTTP
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • GonzoProxy
  • IPOasis
  • Infatica
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy

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
212.50.64.0/198,192BG-BTC-20080104Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PAJan 4, 2008abuse-ip@vivacom.bg
└ 212.50.76.0/221,024TELNET-LIASKOVECTelnet LiaskovecASSIGNED PAJun 12, 2008abuse-ip@vivacom.bg
via BG-BTC-20080104

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

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
Jul 2023
Current origin since
Mar 2024 · 2.6 yr
Origin networks
2
Last change of origin
Mar 2024
Recorded history

History

Handoffs
1