Data as of Nov 14, 2026

212.5.136.0/24

11 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
11
4.3% of its addresses · 30 days
Providers
39
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

738 observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • Ake.net
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • FastProxy
  • GSocks
  • GloryCloud
  • GoProxies
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LemonPrime
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.5.136.0/21
since Dec 2017
AS8866Residential320
52 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
212.5.128.0/198,192BG-BTC-980518Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PA—abuse-ip@vivacom.bg
└ 212.5.136.0/221,024BTC-BROADBAND-NET-22BTC Broadband ServiceASSIGNED PAJun 5, 2015abuse-ip@vivacom.bg
via BG-BTC-980518

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

212.5.136.0/22

Routing history

Pattern
Stable
First seen
Feb 2011
Current origin since
Sep 2014 · 12 yr
Origin networks
2
Last change of origin
Sep 2014
Recorded history

History

Handoffs
1