Data as of Nov 15, 2026

213.91.237.0/24

20 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
20
7.8% of its addresses · 30 days
Providers
36
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • AnyIP
  • BestProxy
  • BirdProxies
  • BuyingProxy
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.91.224.0/19
since Dec 2024
AS8866Residential1,018
222 always on
Vivacom Bulgaria EAD

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.236.0/23512BTC-Broadband-222BTC Broadband servicesASSIGNED PAOct 27, 2008abuse-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

Routing timeline

Covering aggregate above, the prefix's own history below

213.91.236.0/23

Routing history

Pattern
Stable
First seen
Jul 2011
Current origin since
Jul 2011 · 15 yr
Origin networks
1