LAYER3 INTEL
Get started
Sign in
Data as of Nov 10, 2026

213.91.232.0/24

7 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

Announcement
213.91.224.0/19
RPKI valid
Announced by
AS8866
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Always-on exits
1
14% of its exits
Providers
26
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

832 observations

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • FastProxy
  • FloppyData
  • GonzoProxy
  • Infatica
  • Kookey
  • LemonBright
  • Oxylabs
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare

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.232.32/298VIK_ShumenunknownASSIGNED PAMar 30, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.48/298Jambo-Bulgaria_Blv_LANunknownASSIGNED PAMar 30, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.56/298Sokotab-RadinovounknownASSIGNED PAMar 30, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.64/298de-georgo-SofiaunknownASSIGNED PAMar 30, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.72/298SO-Rayon-Novi-Iskar_LANunknownASSIGNED PAApr 2, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.80/298Colonnade_Insurance_S_AunknownASSIGNED PAMay 29, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.88/298OP_transport_LAN4unknownASSIGNED PAApr 2, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.96/298Bulgarian-Burger_Highway-Trakia-296kmunknownASSIGNED PAApr 10, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.104/298Zavodski-Stroeji-Kozlodui-2unknownASSIGNED PAApr 11, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.112/298Chaika-Varna-LAN-1unknownASSIGNED PAApr 12, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.128/298ZlatnaPanega-Sofia-1unknownASSIGNED PAApr 25, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.136/298Zlatna_Panega_Sofia_IlianciunknownASSIGNED PAApr 26, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.144/298ZlatnaPanega-Sofia-VrajdebnaunknownASSIGNED PAApr 26, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.152/298Petrol-Sofia-1unknownASSIGNED PAApr 27, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.160/298Bulgaria-Burger-KulataunknownASSIGNED PAApr 30, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.168/298PhilipMorris-Sofia-LanunknownASSIGNED PAApr 30, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.176/298Tokuda_Bank_Sofia_VideounknownASSIGNED PAMay 2, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.184/298Bulgarian_Burger_Gelemenovo_to_SofiaunknownASSIGNED PAMay 3, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.192/298BulgarianBurger_Gelemenovo-to_BurgasunknownASSIGNED PAMay 3, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.200/298Sanofi-Bulgaria-SofiaunknownASSIGNED PAMay 4, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.208/298Peri-Bulgaria-VrajdebnaunknownASSIGNED PAMar 4, 2021abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.216/298Bulgarian-Burger-PlovdivunknownASSIGNED PAMay 9, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.224/298Embassy-UAE-SofiaunknownASSIGNED PAMay 10, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.232/298UnifyServiceCenter-SofiaunknownASSIGNED PAMay 10, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.240/298Hydrolia-HaskovounknownASSIGNED PAMay 10, 2018abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 213.91.232.248/304Syscom_Gotse_DelchevunknownASSIGNED PAMar 22, 2019abuse-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.

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 213.91.224.0/19

213.91.224.0/19

Routing history

Pattern
Stable
First seen
Dec 2024
Current origin since
Dec 2024 · 1.9 yr
Origin networks
1