Data as of Nov 8, 2026
213.91.135.0/24
2 residential-proxy exits · 30 daysVivacom Bulgaria EAD
Residential-proxy exits
Proxy exits
2
0.78% of its addresses · 30 days
Providers
6
selling exits here
Oct 9, 2026 – Nov 7, 2026
Exits seen per day
30 observations
Proxy providers listing exits
- EnigmaProxy
- FastProxy
- LemonBright
- NovaProxy
- ProxyEmpire
- VantageProxies
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 |
|---|---|---|---|---|---|---|
| 213.91.128.0/17 | 32,768 | BG-BTC-20020905 | Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BG | ALLOCATED PA | Sep 5, 2002 | abuse-ip@ |
| └ 213.91.135.8/29 | 8 | Medico_ | unknown | ASSIGNED PA | Aug 25, 2020 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.16/29 | 8 | BulgarianBurger-Veliko-Tarnovo | unknown | ASSIGNED PA | Aug 26, 2020 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.40/29 | 8 | Atlantis_ | unknown | ASSIGNED PA | Aug 27, 2020 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.48/29 | 8 | Avon_ | unknown | ASSIGNED PA | Mar 9, 2023 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.56/29 | 8 | GenerallyZastrahovane-Pavlikeni | unknown | ASSIGNED PA | Mar 28, 2017 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.64/29 | 8 | GenerallyZastrahovane-Plovdiv-1 | unknown | ASSIGNED PA | Mar 28, 2017 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.72/29 | 8 | GPPPDM-Diadent-Sofia | unknown | ASSIGNED PA | Mar 28, 2017 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.96/29 | 8 | GenerallyZastrahovane-Levski | unknown | ASSIGNED PA | Mar 29, 2017 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.104/29 | 8 | Generally-Shumen | unknown | ASSIGNED PA | Mar 29, 2017 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.120/32 | 1 | GenerallyZastrahovane-Pleven | unknown | ASSIGNED PA | Mar 29, 2017 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.136/29 | 8 | UnionTrans_ | unknown | ASSIGNED PA | Mar 30, 2017 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.152/29 | 8 | GenerallyZastrahovane-Razlog | unknown | ASSIGNED PA | Mar 30, 2017 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.160/29 | 8 | GenerallyZastrahovane-Sandanski | unknown | ASSIGNED PA | Mar 30, 2017 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.168/29 | 8 | GenerallyZastrahovane-Radnevo | unknown | ASSIGNED PA | Mar 31, 2017 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.184/29 | 8 | Rubin-Trading-Pleven-2 | unknown | ASSIGNED PA | Mar 31, 2017 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.192/29 | 8 | Stanga_ | unknown | ASSIGNED PA | Jun 29, 2022 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.200/29 | 8 | GenerallyZastrahovane-Veliko-Tarnovo | unknown | ASSIGNED PA | Apr 3, 2017 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.208/29 | 8 | Bo-D-G-Sofia | unknown | ASSIGNED PA | Apr 3, 2017 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.216/29 | 8 | Bulged-Pleven | unknown | ASSIGNED PA | Apr 5, 2017 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.224/29 | 8 | Velotech_ | unknown | ASSIGNED PA | Dec 21, 2022 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.232/29 | 8 | HospisGriza-Sofia | unknown | ASSIGNED PA | Jul 20, 2018 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.240/30 | 4 | Obshtina_ | unknown | ASSIGNED PA | Feb 7, 2020 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.244/30 | 4 | Obshtina_ | unknown | ASSIGNED PA | Feb 7, 2020 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.248/30 | 4 | Rhenus-Varna_ | unknown | ASSIGNED PA | Nov 8, 2021 | abuse-ip@ via BG-BTC-20020905 |
| └ 213.91.135.252/30 | 4 | Generally-Sofia-bul_ | unknown | ASSIGNED PA | Oct 2, 2019 | abuse-ip@ via BG-BTC-20020905 |
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
256 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Business | 161 | 63% | 23 | |
| Residential | 95 | 37% | 7 |
Network & registry
Origin network
AS8866
BG
- Name
- Vivacom Bulgaria EAD
- Type
- Internet provider
- Registered
- Jul 2, 1998
- Domain
- vivacom.bg
- Website
- www.vivacom.bg
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
- Tor exits
- 1
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Reactivated
- First seen
- May 2005
- Current origin since
- Nov 2025 · 12 mo
- Origin networks
- 2
- Last change of origin
- Nov 2025
Recorded history
History
- Handoffs
- 2
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 213.91.128.0/17 | AS8866 | /24 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS8866 | RIPE | BT95-ADM | Dec 15, 2025 |
Whois
Registration for this announcement
- Range
- 213.
91. 128. 0/ 17 - Netname
- BG-BTC-20020905
- Registrant
- Vivacom Bulgaria EAD
- Registrant country
- BG
- Organization
- Vivacom Bulgaria EAD (ORG-BTCP1-RIPE)
- Org country
- BG
- Type
- ALLOCATED PA
- Created
- Sep 5, 2002
- Updated
- Dec 4, 2020
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- BG
- Delegated
- Sep 5, 2002
- Status
- assigned
Report abuse
Abuse contact
- abuse-ip@
vivacom. bg - Name
- BTC IP ADDRESS SPACE administration
- Handle
- BTC3-RIPE