Data as of Nov 15, 2026

46.10.212.0/23

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

Exits seen per day

1.0K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
46.10.213.0/2413
46.10.212.0/2403

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • GonzoProxy
  • Infatica
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.10.208.0/20
since Oct 2016
AS8866Residential219
19 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
46.10.0.0/1665,536BG-BTC-20100913Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PASep 13, 2010abuse-ip@vivacom.bg
└ 46.10.212.0/23512VilageNETVilageNET Internet ProviderASSIGNED PAApr 20, 2012abuse-ip@vivacom.bg
via BG-BTC-20100913

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
Nov 2011
Current origin since
Mar 2017 · 9.7 yr
Origin networks
1