Data as of Nov 15, 2026

213.16.35.0/24

5 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
52% of it

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Always-on exits
1
20% of its exits
Providers
27
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

2.3K observations
  • Residential
  • Business

Proxy providers listing exits

  • Ake.net
  • BestProxy
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FloppyData
  • GonzoProxy
  • Infatica
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NSocks
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VitalExclusive

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.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.16.32.0/198,192BG-BTC-20011128Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PANov 28, 2001abuse-ip@vivacom.bg
└ 213.16.35.8/298Istoricheski-Park-Heofit-RilskiunknownASSIGNED PASep 23, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.35.16/298National-GalleryNational-GalleryASSIGNED PANov 20, 2015abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.35.24/298ITR-KoprivchitsaunknownASSIGNED PAMar 31, 2016abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.35.56/298SERVIE-BG-NETLaboratories Servie BulgariaASSIGNED PAJun 10, 2004abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.35.64/298AtlanticClub-BG-NETThe Atlantic Club of Bulgaria NetworkASSIGNED PANov 5, 2004abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.35.80/2816SeBordnetCeElectric CompanyASSIGNED PAAug 20, 2003abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.35.100/304Telehause-PazardjikunknownASSIGNED PAMar 5, 2021abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.35.104/298Sofia_ExportSofia ExportASSIGNED PADec 30, 2008abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.35.128/298Bulgarian-DirectReisen_Hotel_PrimorecunknownASSIGNED PAAug 18, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.35.160/2816MaxComwww.sprintmaxcom.comASSIGNED PAAug 8, 2003abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.35.176/304Innovasys-Montana-2unknownASSIGNED PAAug 9, 2022abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.35.188/304Ramus-Medical-Sf-ul_AgnistaunknownASSIGNED PASep 9, 2020abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.35.192/298IAAA-BurgasunknownASSIGNED PAJun 9, 2017abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.35.208/298Hotel_OazisunknownASSIGNED PADec 31, 2018abuse-ip@vivacom.bg
via BG-BTC-20011128
└ 213.16.35.240/298Employment-Agency-Plovdiv-Sofia_Kotlenski_ProhodunknownASSIGNED PADec 6, 2021abuse-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
Residential13252%10
Business12448%15

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
May 2005
Current origin since
Nov 2022 · 4.0 yr
Origin networks
2
Last change of origin
Nov 2022
Recorded history

History

Handoffs
1