LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

5.53.192.0/19

535 residential-proxy exits · 30 days

A1 Bulgaria EAD

Announcement
this exact prefix
RPKI valid
Announced by
AS13124
Type
Residential

Residential-proxy exits

Proxy exits
535
6.5% of its addresses · 30 days
Always-on exits
3
0.56% of its exits
Spread
32 of 32
/24s with at least one exit
Providers
99
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

28K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
5.53.211.0/24131
5.53.218.0/24126
5.53.203.0/2419
5.53.219.0/24036
5.53.216.0/24036
5.53.214.0/24031
5.53.209.0/24029
5.53.217.0/24027
5.53.215.0/24025
5.53.208.0/24022
5.53.210.0/24021
5.53.212.0/24019
5.53.213.0/24019
5.53.222.0/24018
5.53.205.0/24016
5.53.204.0/24014
5.53.192.0/24014
5.53.197.0/24013
5.53.206.0/24012
5.53.223.0/24012
5.53.201.0/24011
5.53.193.0/24011
5.53.195.0/24010
5.53.196.0/24010

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PacketStream
  • PrivateProxy
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RoamProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • TalorData
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalExclusive
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.53.128.0/17
since Feb 2022
AS8717Residential2,163
11 always on
A1 Bulgaria EAD
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
5.53.192.0/22
since Jan 2017
AS13124Residential44A1 Bulgaria EAD
5.53.196.0/22
since Jan 2017
AS13124Residential40A1 Bulgaria EAD
5.53.200.0/22
since Jan 2017
AS13124Residential39
1 always on
A1 Bulgaria EAD
5.53.204.0/22
since Jan 2017
AS13124Residential50A1 Bulgaria EAD
5.53.208.0/21
since Jan 2017
AS13124Residential197
1 always on
A1 Bulgaria EAD
5.53.216.0/22
since Jan 2017
AS13124Residential125
1 always on
A1 Bulgaria EAD
5.53.222.0/23
since Jan 2017
AS13124Residential30A1 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
5.53.128.0/1732,768BG-MTELNET-20120529A1 Bulgaria EAD (ORG-MN1-RIPE) · BGALLOCATED PAMay 29, 2012RIPE.Abuse@a1.bg
└ 5.53.192.0/212,048A1BG-5-plovdiv-jugenplovdivASSIGNED PAJun 29, 2012RIPE.Abuse@a1.bg
via BG-MTELNET-20120529
└ 5.53.200.0/212,048plovdiv-trakiaA1 Bulgaria EADASSIGNED PAJun 29, 2012RIPE.Abuse@a1.bg
via BG-MTELNET-20120529
└ 5.53.208.0/212,048A1BG-5-plovdiv-centerPlovdivASSIGNED PAJun 29, 2012RIPE.Abuse@a1.bg
via BG-MTELNET-20120529
└ 5.53.216.0/221,024A1BG-216-PLovdivPlovdivASSIGNED PAFeb 28, 2013RIPE.Abuse@a1.bg
via BG-MTELNET-20120529
└ 5.53.220.0/23512A1-9unknownASSIGNED PASep 9, 2021RIPE.Abuse@a1.bg
via BG-MTELNET-20120529
└ 5.53.222.0/23512A1BG-Plovdiv-53_222PlovdivASSIGNED PADec 11, 2015RIPE.Abuse@a1.bg
via BG-MTELNET-20120529

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Dec 2012
Current origin since
Aug 2019 · 7.3 yr
Origin networks
1