Data as of Nov 11, 2026

37.63.19.0/24

255 residential-proxy exits · 30 days

A1 Bulgaria EAD

Announcement
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address · Proxy exits nearby

Residential-proxy exits

Proxy exits
255
>99% of its addresses · 30 days
Always-on exits
3
1.2% of its exits
Providers
41
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

73K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CoreProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • Maskify
  • NSocks
  • Novada
  • Oxylabs
  • PacketStream
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
37.63.0.0/17
since Dec 2019
AS8717Residential8,877
76 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
37.63.0.0/1732,768BG-MTELNET-20120123A1 Bulgaria EAD (ORG-MN1-RIPE) · BGALLOCATED PAJan 23, 2012RIPE.Abuse@a1.bg
└ 37.63.16.0/221,024A1-NGN-22unknownASSIGNED PAMay 4, 2020RIPE.Abuse@a1.bg
via BG-MTELNET-20120123

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

37.63.16.0/22

Routing history

Pattern
Stable
First seen
May 2020
Current origin since
Apr 2021 · 5.6 yr
Origin networks
2
Last change of origin
Apr 2021
Recorded history

History

Handoffs
1