Data as of Nov 22, 2026

95.140.221.0/24

26 residential-proxy exits · 30 days

A1 Bulgaria EAD

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

Residential-proxy exits

Proxy exits
26
10% of its addresses · 30 days
Providers
40
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

479 observations

Proxy providers listing exits

  • 911Proxy
  • AnyIP
  • BestProxy
  • BlurPath
  • Byteful
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • FastProxy
  • GEEKPROXY_TURBO
  • GloryCloud
  • IPMUSK
  • IPRoyal
  • KindProxy
  • KocerRoxy
  • LUMIPROXY
  • LemonBright
  • LudaxProxy
  • NSTPROXY_PRIME
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeProxy
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • Q2IP
  • RainProxy
  • RapidProxy
  • Shifter
  • Smartproxy
  • SwiftProxy
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.140.208.0/20
since Feb 2022
AS8717Residential317
2 always on
A1 Bulgaria EAD

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.140.208.0/204,096BG-MTELNET-20090416A1 Bulgaria EAD (ORG-MN1-RIPE) · BGALLOCATED PAApr 16, 2009RIPE.Abuse@a1.bg
└ 95.140.220.0/23512A1-velingradA1 Bulgaria EADASSIGNED PAAug 8, 2011RIPE.Abuse@a1.bg
via BG-MTELNET-20090416

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

95.140.220.0/23

Routing history

Pattern
Stable
First seen
Aug 2009
Current origin since
Nov 2021 · 5.0 yr
Origin networks
2
Last change of origin
Dec 2011
Recorded history

History

Handoffs
1