Data as of Nov 7, 2026
212.25.32.0/19
24 residential-proxy exits · 30 daysVivacom Bulgaria EAD
Residential-proxy exits
Proxy exits
24
0.29% of its addresses · 30 days
Always-on exits
3
13% of its exits
Spread
6 of 32
/24s with at least one exit
Providers
43
selling exits here
Oct 8, 2026 – Nov 6, 2026
Exits seen per day
7.7K observations
- Residential
- Business
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 212.25.61.0/24 | 2 | 13 | |
| 212.25.51.0/24 | 1 | 2 | |
| 212.25.36.0/24 | 0 | 3 | |
| 212.25.44.0/24 | 0 | 3 | |
| 212.25.58.0/24 | 0 | 2 | |
| 212.25.42.0/24 | 0 | 1 |
Proxy providers listing exits
- 2Captcha
- Ake.net
- AnyIP
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- CliProxy
- DataImpulse
- Decodo
- EnigmaProxy
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- GloryCloud
- GonzoProxy
- IPFly
- IPOasis
- Infatica
- KindProxy
- KocerRoxy
- Kookey
- LemonBright
- MangoProxy
- NodeProxy
- NovaProxy
- Oxylabs
- Proxiware
- Proxy-Seller
- ProxyEmpire
- ProxyRack
- Proxyma
- RainProxy
- Shifter
- Smartproxy
- Thordata
- ThunderProxy
- VantageProxies
- VibeProxies
- VitalExclusive
- VitalProxy
Announcements
Nesting
More-specifics by size
Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
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 | ||
| 212.25.48.0/22 since Oct 2024 | AS8866 | Residential | 2 1 always on | Vivacom Bulgaria EAD | |
| 212.25.52.0/24 since Oct 2024 | AS8866 | Residential | Vivacom Bulgaria EAD | ||
| 212.25.56.0/24 since Dec 2022 | AS213357 | Business | Vivacom Bulgaria EAD | ||
| 212.25.61.0/24 since Oct 2024 | AS8866 | Residential | 13 2 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.
| 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 |
| └ 212. | 80 | Drujba3-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.48.80/29 | 8 | ics-bulgaria | Customer ics-bulgaria public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212. | 56 | Drujba3-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.48.144/29 | 8 | precisinter-ktm | Customer precisinter-ktm public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212. | 40 | Drujba3-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.48.192/26 | 64 | wireless-links | IP subnet for wireless devices used for out-of-town links | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.49.0/24 | 256 | Drujba1-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 9, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.50.0/25 | 128 | Maliovica-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.50.128/25 | 128 | CO-Campus-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212. | 148 | Industrial-Zone-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.51.148/30 | 4 | ekon91-firm2 | Customer ekon91-firm2 public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.51.152/29 | 8 | favorit98-firm | Customer favorit98-firm public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.51.160/27 | 32 | ekon91-firm | Customer ekon91-firm public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.51.192/29 | 8 | colocation-rdinkov | Customer public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212. | 56 | Industrial-Zone-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.52.0/25 | 128 | Industrial-Zone2-Mototehnika-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.52.128/25 | 128 | Melnicata-Pub-IPs | Customers with no-dialup public IPs | ASSIGNED PA | Sep 15, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.53.0/24 | 256 | RAS-Day2-PPPoE | IPs for masquerading PPPoE dialup users | ASSIGNED PA | Sep 9, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.54.0/24 | 256 | Interconnect-subnets | IP space userd for interconnect and ISP customers | ASSIGNED PA | Nov 16, 2022 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.55.0/24 | 256 | Terranet | Terranet IP space | ASSIGNED PA | Nov 24, 2022 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.56.0/24 | 256 | Kaolin | Kaolin AD IP space | ASSIGNED PA | Nov 24, 2022 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.57.0/24 | 256 | Interconnect-subnets | IP space userd for interconnect and ISP customers | ASSIGNED PA | Nov 24, 2022 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.58.0/24 | 256 | Clients-Ruse | Clients-Ruse | ASSIGNED PA | Sep 8, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.59.0/24 | 256 | RAS-Traf2-PPPoE | IPs for masquerading PPPoE dialup users | ASSIGNED PA | Sep 9, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.60.0/24 | 256 | RAS-Day1-PPPoE | IPs for masquerading PPPoE dialup users | ASSIGNED PA | Sep 9, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.61.0/24 | 256 | Zdravec-Sever-PPPoE | Customers with PPPoE dialup public IPs | ASSIGNED PA | Sep 21, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.62.0/24 | 256 | RAS-Day2-PPTP | IPs for masquerading PPTP dialup users | ASSIGNED PA | Sep 9, 2009 | abuse-ip@ via BG-BTC-20051025 |
| └ 212.25.63.0/24 | 256 | RAS-Day1-PPTP | IPs for masquerading PPTP dialup users | ASSIGNED PA | Feb 23, 2007 | 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
8,192 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 5,940 | 73% | 18 | |
| Business | 2,252 | 27% | 48 |
Network & registry
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 this prefix
Summary
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
IRR
Route objects on the exact prefix
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 212.25.32.0/20 | AS34569 | RIPE | NETWORX-BG, Aggregated Provider Local Registry Block | NETWORX-BG | Oct 26, 2005 |
| 212.25.32.0/21 | AS8866 | RIPE | BT95-ADM | Oct 25, 2024 | |
| 212.25.39.0/24 | AS34569 | RIPE | NETWORX-BG, Aggregated Provider Local Registry Block | NETWORX-BG | Jan 3, 2007 |
| 212.25.40.0/21 | AS8866 | RIPE | BT95-ADM | Oct 25, 2024 | |
| 212.25.43.0/24 | AS34569 | RIPE | NETWORX-BG Ltd. Traffic Subscribers PPPoE2 | NETWORX-BG | Mar 16, 2007 |
| 212.25.47.0/24 | AS34569 | RIPE | NETWORX-BG, Aggregated Provider Local Registry Block | NETWORX-BG | Jan 3, 2007 |
| 212.25.48.0/20 | AS34569 | RIPE | NETWORX-BG, Aggregated Provider Local Registry Block | NETWORX-BG | Oct 26, 2005 |
| 212.25.48.0/21 | AS8866 | RIPE | BT95-ADM | Oct 25, 2024 | |
| 212.25.53.0/24 | AS34569 | RIPE | NETWORX-BG Ltd. Home-unl-PPPoE2 | NETWORX-BG | Dec 2, 2006 |
| 212.25.54.0/24 | AS34569 | RIPE | NETWORX-BG | Nov 24, 2022 | |
| 212.25.55.0/24 | AS215342 | RIPE | BT95-ADM | May 27, 2024 | |
| 212.25.57.0/24 | AS34569 | RIPE | Networx-BG | NETWORX-BG | Apr 25, 2014 |
| 212.25.58.0/24 | AS34569 | RIPE | NETWORX-BG Ltd. Routers | NETWORX-BG | Dec 1, 2006 |
| 212.25.59.0/24 | AS34569 | RIPE | NETWORX-BG Ltd. Traf1-PPPoE | NETWORX-BG | Nov 13, 2006 |
| 212.25.60.0/24 | AS34569 | RIPE | NETWORX-BG Ltd. Day-PPPoE | NETWORX-BG | Feb 7, 2006 |
| 212.25.62.0/24 | AS34569 | RIPE | NETWORX-BG Ltd. - Razgrad | NETWORX-BG | Jul 19, 2016 |
| 212.25.63.0/24 | AS34569 | RIPE | NETWORX-BG, Aggregated Provider Local Registry Block | NETWORX-BG | Nov 15, 2005 |
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