Data as of Nov 12, 2026

212.5.136.0/22

51 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
51
5.0% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
61
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

4.3K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
212.5.139.0/24014
212.5.138.0/24013
212.5.136.0/24012
212.5.137.0/24012

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • LUMIPROXY
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.5.136.0/21
since Dec 2017
AS8866Residential318
47 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
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

Summary

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