Data as of Nov 10, 2026

213.91.167.0/24

6 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
6
2.3% of its addresses · 30 days
Providers
19
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

144 observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • BestProxy
  • BirdProxies
  • EnigmaProxy
  • FastProxy
  • LUMIPROXY
  • LemonBright
  • MangoProxy
  • NSocks
  • NiuProxy
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.91.160.0/21
since Oct 2022
AS8866Residential17Vivacom 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.167.0/24256BTC-BROADBAND-NET-88BTC Broadband ServiceASSIGNED PAOct 3, 2006abuse-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
Nov 2014 · 12 yr
Origin networks
2
Last change of origin
Nov 2014
Recorded history

History

Handoffs
2