Data as of Nov 14, 2026

84.252.1.0/24

2 residential-proxy exits · 30 days

A1 Bulgaria EAD

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

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Always-on exits
1
50% of its exits
Providers
33
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

14K observations

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • EZProxies
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPPeak
  • IPRoyal
  • Infatica
  • LudaxProxy
  • MoMoProxy
  • Oxylabs
  • Proxio
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • RainProxy
  • StrikeProxy
  • Thordata
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
84.252.0.0/18
since Feb 2022
AS8717Residential970
14 always on
A1 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
84.252.0.0/1816,384BG-MTELNET-20040908A1 Bulgaria EAD (ORG-MN1-RIPE) · BGALLOCATED PASep 8, 2004RIPE.Abuse@a1.bg
└ 84.252.0.0/212,048HaskovoA1 HaskovoASSIGNED PAJun 2, 2008RIPE.Abuse@a1.bg
via BG-MTELNET-20040908

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
Apr 2010
Current origin since
May 2021 · 5.5 yr
Origin networks
1