Data as of Nov 19, 2026

212.50.90.0/23

16 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
16
3.1% of its addresses · 30 days
Always-on exits
1
6.3% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
40
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

2.4K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
212.50.90.0/24111
212.50.91.0/2405

Proxy providers listing exits

  • 2Captcha
  • 911Proxy
  • 9HTTP
  • APROXY
  • ASHBURNPROXIES
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • Decodo
  • FastProxy
  • FlashProxy
  • FloppyData
  • GonzoProxy
  • Infatica
  • KocerRoxy
  • LUMIPROXY
  • LemonBright
  • LightningProxies
  • NSocks
  • NiuProxy
  • Oxylabs
  • PROXY_CC
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

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.90.0/23512TELNET-DEBELECTelnet Limited - DebelecASSIGNED PASep 29, 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
Oct 2008
Current origin since
Mar 2024 · 2.6 yr
Origin networks
2
Last change of origin
Mar 2024
Recorded history

History

Handoffs
1