Data as of Nov 20, 2026

213.91.202.40/29

1 residential-proxy exit · 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
1
13% of its addresses · 30 days
Always-on exits
1
100% of its exits
Providers
42
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

44 observations

Proxy providers listing exits

  • 711Proxy
  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • BottingTools
  • Byteful
  • CYBERYOZH
  • DataImpulse
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlashProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonode
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • Kookey
  • LemonBright
  • MangoProxy
  • NodeProxy
  • Novada
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.91.200.0/21
since Dec 2024
AS8866Residential40
4 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.202.40/298ElenaGroup-PopovounknownASSIGNED PAJul 19, 2018abuse-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.202.0/24

Routing history

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