Data as of Nov 7, 2026
212.25.32.0/20
7 residential-proxy exits · 30 daysVivacom Bulgaria EAD
Residential-proxy exits
Proxy exits
7
0.17% of its addresses · 30 days
Spread
3 of 16
/24s with at least one exit
Providers
27
selling exits here
Oct 8, 2026 – Nov 6, 2026
Exits seen per day
477 observations
- Residential
- Business
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 212.25.36.0/24 | 0 | 3 | |
| 212.25.44.0/24 | 0 | 3 | |
| 212.25.42.0/24 | 0 | 1 |
Proxy providers listing exits
- 2Captcha
- AnyIP
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- CliProxy
- EnigmaProxy
- FastProxy
- FlashProxy
- FloppyData
- GonzoProxy
- Infatica
- KocerRoxy
- LemonBright
- MangoProxy
- NodeProxy
- NovaProxy
- Proxiware
- Proxy-Seller
- ProxyEmpire
- ProxyRack
- Proxyma
- Shifter
- Thordata
- ThunderProxy
- VitalExclusive
Announcements
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 212.25.32.0/22 since Oct 2024 | AS8866 | Residential | Vivacom Bulgaria EAD | ||
| 212.25.36.0/23 since Oct 2024 | AS8866 | Residential | 3 | Vivacom Bulgaria EAD | |
| 212.25.38.0/24 since Oct 2024 | AS8866 | Residential | Vivacom Bulgaria EAD | ||
| 212.25.40.0/23 since Oct 2024 | AS8866 | Residential | Vivacom Bulgaria EAD | ||
| 212.25.42.0/24 since Oct 2024 | AS8866 | Residential | 1 | Vivacom Bulgaria EAD | |
| 212.25.44.0/23 since Oct 2024 | AS8866 | Residential | 3 | Vivacom Bulgaria EAD | |
| 212.25.46.0/24 since Oct 2024 | AS8866 | Residential | Vivacom Bulgaria EAD |
Registrations in this block
The registry's network records over this block, widest first, each under its parent.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 212.25.32.0/19 | 8,192 | BG-BTC-20051025 | Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BG | ALLOCATED PA | Oct 25, 2005 | abuse-ip@ |
| └ 212.25.32.0/24 | 256 | Center1-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 9, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.33.0/27 | 32 | VZ-2-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.33.32/27 | 32 | Zala-Fonbox | Customer Zala-Fonbox subnet | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212. | 192 | VZ-2-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.34.0/24 | 256 | VZ-3-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 9, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.35.0/26 | 64 | Center1-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.35.64/27 | 32 | zala-dexter2 | Customer zala-dexter2 subnet | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.35.96/29 | 8 | Runel2008 | Customer runel2008 subnet | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212. | 152 | Center1-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.36.0/28 | 16 | Center2-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212. | 48 | Kovashki-servers | Customers kovashki-servers subner | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.36.64/29 | 8 | Center2-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.36.72/29 | 8 | appd-baza | Customer appd-baza subnet | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212. | 56 | Center2-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.36.136/29 | 8 | Vitosha | Customer vitosha public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.36.144/28 | 16 | Center2-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.36.160/29 | 8 | hotel-cosmopolitan | Customer hotel-cosmopolitan public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212. | 56 | Center2-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.36.224/27 | 32 | zala-dexter-center2 | Customer zala-dexter-center2 public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212. | 144 | Borisova-new-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.37.144/29 | 8 | parallelbg-server | Customer parallelbg-server public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212. | 40 | Borisova-new-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.37.192/27 | 32 | zala-dexter3 | Customer zala-dexter3 public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.37.224/27 | 32 | Borisova-new-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.38.0/24 | 256 | Borisova-old-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 9, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.39.0/24 | 256 | RAS-Day1-2-PPPoE | IPs for masquerading PPPoE dialup users | ASSIGNED PA | Sep 9, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.40.0/27 | 32 | Rodina-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.40.32/27 | 32 | zala-minimax | Customer zala-minimax public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212. | 80 | Rodina-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.40.144/28 | 16 | zala-ruchi | Customer zala-ruchi public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212. | 96 | Rodina-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.41.0/24 | 256 | Zdravec-old-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 9, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.42.0/28 | 16 | Zdravec-North-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.42.16/28 | 16 | zali-parij2 | Customer zali-parij public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.42.32/27 | 32 | Zdravec-North-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.42.64/26 | 64 | zali-parij1 | Customer zali-parij1 public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.42.128/27 | 32 | Zdravec-North-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.42.160/27 | 32 | Industrial3-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.42.192/26 | 64 | RadoB-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.43.0/24 | 256 | RAS-Traf1-PPPoE | IPs for masquerading PPPoE dialup users | ASSIGNED PA | Sep 9, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212. | 72 | Zdravec-Iztok-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.44.72/29 | 8 | montupet | Customer montupet public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212. | 176 | Zdravec-Iztok-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.45.0/24 | 256 | Charodeika-South-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 9, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.46.0/24 | 256 | Charodeika-North-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 9, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.47.0/24 | 256 | RAS-Day2-1-PPPoE | IPs for masquerading PPPoE dialup users | ASSIGNED PA | Sep 9, 2009 | abuse-ip@ 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
4,096 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 2,968 | 72% | 11 | |
| Business | 1,128 | 28% | 33 |
Network & registry
Announced by
Covering announcement 212.25.32.0/19
- Prefix
- 212.25.32.0/19
- Announced by
- AS34569 Vivacom Bulgaria EAD
- Type
- Residential
- Proxy exits
- 24
- Always-on exits
- 3
- RPKI
- RPKI valid
- Netname
- BG-BTC-20051025
- Registrant
- Vivacom Bulgaria EAD
- RIR
- RIPE NCC
Origin network
AS34569
BG
- Name
- Vivacom Bulgaria EAD
- Type
- Internet provider
- Registered
- Feb 16, 2005
- Domain
- vivacom.bg
- Website
- www.vivacom.bg
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
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
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 212.25.32.0/19 | AS8866 | /24 | RIPE | Another network |
| 212.25.32.0/19 | AS34569 | /24 | RIPE | RPKI valid |
Whois
Registration for this announcement
- Range
- 212.
25. 32. 0/ 19 - Netname
- BG-BTC-20051025
- Registrant
- Vivacom Bulgaria EAD
- Registrant country
- BG
- Organization
- Vivacom Bulgaria EAD (ORG-BTCP1-RIPE)
- Org country
- BG
- Type
- ALLOCATED PA
- Created
- Oct 25, 2005
- Updated
- May 14, 2024
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- BG
- Delegated
- Oct 25, 2005
- Status
- assigned
Report abuse
Abuse contact
- abuse-ip@
vivacom. bg - Name
- BTC IP ADDRESS SPACE administration
- Handle
- BTC3-RIPE