Data as of Nov 18, 2026

212.25.36.0/23

4 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business
72% of it

Residential-proxy exits

Proxy exits
4
0.78% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
23
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

637 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
212.25.36.0/2403
212.25.37.0/2401

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • FastProxy
  • FlashProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GonzoProxy
  • Infatica
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.25.32.0/19
since Jan 2008
AS34569Residential30
3 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
212.25.32.0/198,192BG-BTC-20051025Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PAOct 25, 2005abuse-ip@vivacom.bg
└ 212.25.36.0/2816Center2-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.36.16 - 212.25.36.6348Kovashki-serversCustomers kovashki-servers subnerASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.36.64/298Center2-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.36.72/298appd-bazaCustomer appd-baza subnetASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.36.80 - 212.25.36.13556Center2-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.36.136/298VitoshaCustomer vitosha public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.36.144/2816Center2-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.36.160/298hotel-cosmopolitanCustomer hotel-cosmopolitan public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.36.168 - 212.25.36.22356Center2-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.36.224/2732zala-dexter-center2Customer zala-dexter-center2 public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.37.0 - 212.25.37.143144Borisova-new-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.37.144/298parallelbg-serverCustomer parallelbg-server public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.37.152 - 212.25.37.19140Borisova-new-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.37.192/2732zala-dexter3Customer zala-dexter3 public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.37.224/2732Borisova-new-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

512 addresses
TypeAddressesShareRanges
Business36872%14
Residential14428%1

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Oct 2024
Current origin since
Oct 2024 · 2.1 yr
Origin networks
1