Data as of Nov 19, 2026

185.177.32.0/22

9 residential-proxy exits · 30 days

Azienda Pubbliservizi Brunico

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

Residential-proxy exits

Proxy exits
9
0.88% of its addresses · 30 days
Always-on exits
1
11% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
43
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

9.4K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • AETHYN_ELITE
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • CoreProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • MoMoProxy
  • NovProxy
  • NovaProxy
  • PacketStream
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Shifter
  • VantageProxies
  • VitalExclusive

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
185.177.32.0/221,024IT-BRUNETZ-20161110Azienda Pubbliservizi Brunico (ORG-APB1-RIPE) · ITALLOCATED PANov 10, 2016ripe-abuse@stadtwerke.it
└ 185.177.32.0/24256SW-NETunknownASSIGNED PAMar 9, 2020ripe-abuse@stadtwerke.it
via IT-BRUNETZ-20161110
└ 185.177.33.0/24256SW-NETStadtwerke Bruneck - Azienda Pubbliservizi BrunicoASSIGNED PAMar 9, 2020ripe-abuse@stadtwerke.it
via IT-BRUNETZ-20161110
└ 185.177.34.0/24256SW-NETStadtwerke Bruneck - Azienda Pubbliservizi BrunicoASSIGNED PAMar 9, 2020ripe-abuse@stadtwerke.it
via IT-BRUNETZ-20161110
└ 185.177.35.0/24256SW-NETStadtwerke Bruneck - Azienda Pubbliservizo BrunicoASSIGNED PAMar 9, 2020ripe-abuse@stadtwerke.it
via IT-BRUNETZ-20161110

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Mar 2020
Current origin since
Mar 2020 · 6.7 yr
Origin networks
1