Data as of Nov 14, 2026

90.154.238.0/23

32 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
32
6.3% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
63
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

3.3K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
90.154.238.0/24018
90.154.239.0/24014

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • AnyIP
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HELODATA
  • IPFly
  • IPMUSK
  • IPPeak
  • Infatica
  • KindProxy
  • KocerRoxy
  • LUMIPROXY
  • LemonBright
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYSALE
  • PROXYSCRAPE
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • Smartproxy
  • SwiftProxy
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
90.154.128.0/17
since Nov 2006
AS8866Residential7,967
28 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
90.154.128.0/1732,768BG-BTC-20061114Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PANov 14, 2006abuse-ip@vivacom.bg
└ 90.154.238.0/23512BTC-BROADBAND-NET-26BTC Broadband ServiceASSIGNED PAJun 5, 2015abuse-ip@vivacom.bg
via BG-BTC-20061114

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
Nov 2013
Current origin since
Jan 2015 · 12 yr
Origin networks
2
Last change of origin
Jan 2015
Recorded history

History

Handoffs
1