Data as of Nov 17, 2026

213.91.159.0/24

2 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

Announcement
RPKI valid
Announced by
Type
Business
51% of it

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
20
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

899 observations

Proxy providers listing exits

  • 9HTTP
  • Byteful
  • CliProxy
  • FastProxy
  • GSocks
  • Geonix
  • HASDATA
  • IPPeak
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxyma
  • RainProxy
  • Shifter

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.91.128.0/1732,768BG-BTC-20020905Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PASep 5, 2002abuse-ip@vivacom.bg
└ 213.91.159.0/298Telerik-AD_SofiaunknownASSIGNED PAMay 16, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.159.24/298Museum_IskraunknownASSIGNED PAMar 29, 2017abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.159.40/298Obshtina_Roman_ODZ_ZoraunknownASSIGNED PAAug 20, 2020abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.159.52/304Samitash-Metalbau-KuklenunknownASSIGNED PAFeb 18, 2019abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.159.80/298Perla-TuristPerla-TuristASSIGNED PADec 14, 2015abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.159.96/298Mikroak-BotevgradunknownASSIGNED PADec 2, 2016abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.159.104/304Lukoil-Elenino-PSB-Stara-ZagoraunknownASSIGNED PAJul 28, 2020abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.159.108/304Lukoil-Sofia-PSB-IliyanciunknownASSIGNED PAJul 29, 2020abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.159.128 - 213.91.159.1336Pechatnitsa_Sofia_EOODunknownASSIGNED PAOct 28, 2016abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.159.136/298Cefin-BGCefin Bulgaria OODASSIGNED PAAug 27, 2014abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.159.144/298MelonunknownASSIGNED PAMay 5, 2016abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.159.160/298Maxcom-RadinovounknownASSIGNED PAJun 30, 2022abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.159.168/298DHL-HaskovounknownASSIGNED PAJun 6, 2022abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.159.192/298InternetUslugiKomunikacii-Sofia-5030unknownASSIGNED PAApr 12, 2022abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.159.200/298Employment-Agency-BorovanunknownASSIGNED PAMar 4, 2022abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.159.216/298Employment-Agency-BurgasunknownASSIGNED PAMar 4, 2022abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.159.232/298IAAA-PernikunknownASSIGNED PAJul 4, 2017abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.159.240/298Global_Solutions_LTDunknownASSIGNED PAApr 12, 2021abuse-ip@vivacom.bg
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
TypeAddressesShareRanges
Business13051%18
Residential12649%12

Network & registry

Routing timeline

Who has announced 213.91.158.0/23

213.91.158.0/23

Routing history

Pattern
Stable
First seen
Mar 2025
Current origin since
Mar 2025 · 1.7 yr
Origin networks
1