Data as of Nov 18, 2026

213.91.204.4/30

No anonymizer space · no proxy exits in 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
6
100% of its addresses · listed by providers
Providers
41
selling exits here

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • AnyIP
  • BestProxy
  • BirdProxies
  • ByteProxies
  • Byteful
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • GonzoProxy
  • IPOasis
  • Infatica
  • KocerRoxy
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • ThunderProxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.91.200.0/21
since Dec 2024
AS8866Residential39
5 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.204.4/304OP-Transport-Bolard-ChadaraunknownASSIGNED PAAug 28, 2020abuse-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.204.0/24

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Nov 2021 · 5.0 yr
Origin networks
1