Data as of Nov 20, 2026

213.91.235.0/24

7 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Providers
29
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

564 observations

Proxy providers listing exits

  • AETHYN_ELITE
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • GEEKPROXY_FLEX
  • GSocks
  • Infatica
  • LemonBright
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.91.224.0/19
since Dec 2024
AS8866Residential1,035
256 always on
Vivacom Bulgaria EAD

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.91.128.0/1732,768BG-BTC-20020905Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PASep 5, 2002abuse-ip@vivacom.bg
└ 213.91.235.0/24256WAN7-BTC-NETWan Point-to-Point linksASSIGNED PAApr 22, 2004abuse-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

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1