Data as of Nov 16, 2026

212.25.40.0/21

4 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

Announcement
RPKI valid
Announced by
Type
Residential
71% of it

Residential-proxy exits

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

Exits seen per day

75 observations
  • Residential
  • Business

/24s with the most always-on exits

/24Always-on exitsProxy exits
212.25.44.0/2403
212.25.42.0/2401

Proxy providers listing exits

  • AnyIP
  • FastProxy
  • FloppyData
  • KocerRoxy
  • LemonBright
  • ProxyRack
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
212.25.40.0/23
since Oct 2024
AS8866ResidentialVivacom Bulgaria EAD
212.25.42.0/24
since Oct 2024
AS8866Residential1Vivacom Bulgaria EAD
212.25.44.0/23
since Oct 2024
AS8866Residential3Vivacom Bulgaria EAD
212.25.46.0/24
since Oct 2024
AS8866ResidentialVivacom Bulgaria EAD

Registrations in this block

The registry's network records over this block, widest first, each 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.40.0/2732Rodina-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.40.32/2732zala-minimaxCustomer zala-minimax public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.40.64 - 212.25.40.14380Rodina-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.40.144/2816zala-ruchiCustomer zala-ruchi public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.40.160 - 212.25.40.25596Rodina-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.41.0/24256Zdravec-old-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 9, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.42.0/2816Zdravec-North-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.42.16/2816zali-parij2Customer zali-parij public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.42.32/2732Zdravec-North-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.42.64/2664zali-parij1Customer zali-parij1 public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.42.128/2732Zdravec-North-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.42.160/2732Industrial3-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.42.192/2664RadoB-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.43.0/24256RAS-Traf1-PPPoEIPs for masquerading PPPoE dialup usersASSIGNED PASep 9, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.44.0 - 212.25.44.7172Zdravec-Iztok-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.44.72/298montupetCustomer montupet public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.44.80 - 212.25.44.255176Zdravec-Iztok-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 15, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.45.0/24256Charodeika-South-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 9, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.46.0/24256Charodeika-North-Pub-IPsCustomers with no-dialup public IPsASSIGNED PASep 9, 2009abuse-ip@vivacom.bg
via BG-BTC-20051025
└ 212.25.47.0/24256RAS-Day2-1-PPPoEIPs for masquerading PPPoE dialup usersASSIGNED PASep 9, 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

2,048 addresses
TypeAddressesShareRanges
Residential1,45671%5
Business59229%14

Network & registry

Routing timeline

Who has announced 212.25.32.0/19

212.25.32.0/19

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Jan 2008 · 19 yr
Origin networks
2
Last change of origin
Jan 2008
Recorded history

History

Handoffs
1