Data as of Nov 13, 2026

46.238.24.0/23

22 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
22
4.3% of its addresses · 30 days
Always-on exits
2
9.1% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
61
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

4.4K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
46.238.24.0/24211
46.238.25.0/24011

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • GhostConnect
  • GonzoProxy
  • HydraProxy
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYON
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.238.0.0/18
since May 2024
AS8717Residential164
10 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
46.238.0.0/1816,384BG-MTELNET-20110131A1 Bulgaria EAD (ORG-MN1-RIPE) · BGALLOCATED PAJan 31, 2011RIPE.Abuse@a1.bg
└ 46.238.24.0/212,048KRASNAPOLIANA-NET-SOFMegalan Network Ltd.ASSIGNED PAFeb 2, 2011RIPE.Abuse@a1.bg
via BG-MTELNET-20110131

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
Mar 2026
Current origin since
Mar 2026 · 8 mo
Origin networks
1