Data as of Nov 21, 2026

217.18.254.0/23

4 residential-proxy exits · 30 days

A1 Bulgaria EAD

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
4
0.78% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
20
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

114 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
217.18.254.0/2403
217.18.255.0/2401

Proxy providers listing exits

  • Ake.net
  • AnyIP
  • BlurPath
  • DataImpulse
  • FastProxy
  • GloryCloud
  • IPFly
  • KindProxy
  • KocerRoxy
  • LemonBright
  • MoMoProxy
  • NSocks
  • NextProxy
  • Proxmint
  • Proxy4U
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • Smartproxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
217.18.240.0/20
since Feb 2022
AS8717Residential91
5 always on
A1 Bulgaria EAD
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
217.18.254.0/24
since Nov 2021
AS13124Residential3A1 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
217.18.240.0/204,096BG-MTELNET-20030120A1 Bulgaria EAD (ORG-MN1-RIPE) · BGALLOCATED PAJan 20, 2003RIPE.Abuse@a1.bg
└ 217.18.254.0/24256BGCOMBgcom.net Ltd.ASSIGNED PANov 17, 2004RIPE.Abuse@a1.bg
via BG-MTELNET-20030120
└ 217.18.255.0/24256Plovdiv-255-28unknownASSIGNED PASep 28, 2017RIPE.Abuse@a1.bg
via BG-MTELNET-20030120

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 2017
Current origin since
Mar 2017 · 9.7 yr
Origin networks
1