Data as of Nov 20, 2026

213.16.48.0/24

3 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

Announcement
RPKI valid
Announced by
Type
Business
61% of it

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
6
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

26 observations

Proxy providers listing exits

  • FastProxy
  • GSocks
  • LemonBright
  • NodeProxy
  • Proxy-Seller
  • ThunderProxy

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.16.32.0/198,192BG-BTC-20011128Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PANov 28, 2001abuse-ip@vivacom.bg
└ 213.16.48.0/2816Deroni_Stara-ZagoraunknownASSIGNED PAMar 5, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.16/304Municipal_Iskar_ChitalishteunknownASSIGNED PAApr 2, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.20/304Municipal_Iskat_Inet3unknownASSIGNED PAApr 2, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.64/298Obshtina_Maglizh_StadionaunknownASSIGNED PAApr 3, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.72/304Obshtina_Maglizh_Chitalishte_ProbudaunknownASSIGNED PAApr 3, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.76/304Obstina-Iskar-Sport-placeunknownASSIGNED PAApr 7, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.80/298BugarianBurger-RuseunknownASSIGNED PAApr 3, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.88/298Obshtina_Maglizh_Lan3unknownASSIGNED PAApr 6, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.96/298Obshtina_Maglizh_ul_3_ti_32_MartunknownASSIGNED PAApr 6, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.104/298NOI-Sofia-Maldost-3unknownASSIGNED PAApr 8, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.112/298NOI-Stara-Zagora-1unknownASSIGNED PAApr 9, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.120/298Boroinvest_ADunknownASSIGNED PADec 21, 2021abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.128/298Yoni_DM-YonkoStoilov-SofiaunknownASSIGNED PAApr 10, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.136/298NOI-Kyistendil-1unknownASSIGNED PAApr 10, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.152/298NOI-Targovishte-1unknownASSIGNED PAApr 13, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.160/298Progredit-Bank-Sofia-3DCunknownASSIGNED PAApr 13, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.184/298National_Center_of_Infectious_and_Parasitic_DiseasesunknownASSIGNED PAApr 16, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.200/298NOI-MontanaunknownASSIGNED PAApr 21, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.208/298SBAL-Po-Ortopedia-Boycho-BoichevunknownASSIGNED PAApr 23, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.232/298Trace_Group_HoldingunknownASSIGNED PAApr 30, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.48.252/304Syscom_Agencia_Zaetost_DospatunknownASSIGNED PAOct 8, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128

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
TypeAddressesShareRanges
Business15661%21
Residential10039%6

Network & registry

Routing timeline

Who has announced 213.16.48.0/20

213.16.48.0/20

Routing history

Pattern
Stable
First seen
Dec 2022
Current origin since
Dec 2022 · 4.0 yr
Origin networks
1