Data as of Nov 15, 2026

213.16.45.0/24

6 residential-proxy exits · 30 days

AS197050 · space held by Vivacom Bulgaria EAD

Announcement
this exact prefix
RPKI valid
Announced by
Type
Unknown
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Providers
56
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

8.5K observations

Proxy providers listing exits

  • 711Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPMUSK
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • KindProxy
  • LemonBright
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • MoMoProxy
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PacketStream
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • RapidProxy
  • Shifter
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • Webshare
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.16.40.0/21
since Dec 2022
AS8866Residential33
5 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
213.16.32.0/198,192BG-BTC-20011128Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PANov 28, 2001abuse-ip@vivacom.bg
└ 213.16.45.0/24256BORIANAGROUP-BG-NET # 1IP space for Boriana-GroupASSIGNED PAJun 7, 2005abuse-ip@vivacom.bg
via BG-BTC-20011128

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
Jun 2005
Current origin since
Oct 2011 · 15 yr
Origin networks
2
Last change of origin
Oct 2011
Recorded history

History

Handoffs
1