Data as of Nov 13, 2026

95.43.202.0/24

14 residential-proxy exits · 30 days

Turbo-Net EOOD · space held by Vivacom Bulgaria EAD

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
14
5.5% of its addresses · 30 days
Always-on exits
3
21% of its exits
Providers
60
selling exits here
Oct 14, 2026 – Nov 11, 2026

Exits seen per day

20K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPCola
  • IPFly
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonBright
  • LemonPrime
  • MangoProxy
  • Maskify
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • RapidProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalExclusive
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.43.200.0/22
since Jan 2025
AS8866Residential24
3 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
95.42.0.0/15131,072BG-BTC-20081015Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PAOct 15, 2008abuse-ip@vivacom.bg
└ 95.43.202.0/24256TurbonetTurbonet-2ASSIGNED PAMay 28, 2010abuse-ip@vivacom.bg
via BG-BTC-20081015

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 2010
Current origin since
Jun 2017 · 9.4 yr
Origin networks
2
Last change of origin
Jun 2017
Recorded history

History

Handoffs
1