Data as of Nov 21, 2026

213.16.42.0/29

1 residential-proxy exit · 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
1
13% of its addresses · 30 days
Providers
30
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

37 observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GSocks
  • GonzoProxy
  • Infatica
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • SOTAPROXY
  • Shifter
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.16.40.0/21
since Dec 2022
AS8866Residential35
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.16.32.0/198,192BG-BTC-20011128Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PANov 28, 2001abuse-ip@vivacom.bg
└ 213.16.42.0/298PGEE-Konstantin-Fotinov-Burgas_LAN1unknownASSIGNED PAJul 29, 2019abuse-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

213.16.42.0/24

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1