Data as of Nov 17, 2026

213.91.148.0/23

9 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
9
1.8% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
26
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

239 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
213.91.148.0/2406
213.91.149.0/2402

Proxy providers listing exits

  • 9HTTP
  • BirdProxies
  • Byteful
  • DataImpulse
  • Decodo
  • EVOPROXY
  • GSocks
  • GloryCloud
  • IPFly
  • IPMUSK
  • Infatica
  • LemonBright
  • MangoProxy
  • NSocks
  • NextProxy
  • NodeProxy
  • Oxylabs
  • Proxmint
  • Proxy4U
  • ProxyEmpire
  • ProxyWing
  • RH7Proxy
  • RainProxy
  • Shifter
  • Thordata
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.91.144.0/21
since Mar 2025
AS8866Residential20Vivacom 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.148.0/23512BTC-BROADBAND-NETBTC Broadband ServiceASSIGNED PAJan 10, 2019abuse-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
Dec 2005
Current origin since
Jan 2019 · 7.9 yr
Origin networks
3
Last change of origin
Jan 2019
Recorded history

History

Handoffs
3