Data as of Nov 15, 2026

217.79.45.0/24

12 residential-proxy exits · 30 days

A1 Bulgaria EAD

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

Residential-proxy exits

Proxy exits
12
4.7% of its addresses · 30 days
Providers
38
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

677 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • APROXY
  • AnyIP
  • BestProxy
  • BirdProxies
  • ByteProxies
  • Byteful
  • CROXY
  • EnigmaProxy
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GonzoProxy
  • HydraProxy
  • IPOasis
  • Infatica
  • KocerRoxy
  • LUMIPROXY
  • LemonBright
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
217.79.32.0/20
since May 2016
AS8717Residential81
7 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
217.79.32.0/204,096BG-MTELNET-20001228A1 Bulgaria EAD (ORG-MN1-RIPE) · BGALLOCATED PA—RIPE.Abuse@a1.bg
└ 217.79.44.0/221,024SPNET-PON-Varna-4unknownASSIGNED PAJun 2, 2016RIPE.Abuse@a1.bg
via BG-MTELNET-20001228

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

217.79.44.0/22

Routing history

Pattern
Stable
First seen
May 2016
Current origin since
Jan 2021 · 5.8 yr
Origin networks
1