Data as of Nov 22, 2026

79.135.160.0/19

112 residential-proxy exits · 30 days

Bialogardzka Spoldzielnia Mieszkaniowa

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

Residential-proxy exits

Proxy exits
112
1.4% of its addresses · 30 days
Always-on exits
9
8.0% of its exits
Spread
28 of 32
/24s with at least one exit
Providers
101
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

33K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9Proxy
  • AETHYN_BASIC
  • AETHYN_ELITE
  • Ake.net
  • AnyIP
  • B2Proxy
  • BUYPERSONALPROXY
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • DATAIMPULSE_PREMIUM
  • DataImpulse
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HASDATA
  • HELODATA
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • LOKIPROXY
  • LemonBright
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSTPROXY_LITE
  • NSTPROXY_PRIME
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXIWARE_ECO
  • PROXYLANE
  • PROXYSAVER
  • PROXYSCRAPE
  • PYPROXY
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • SCRAPELESS
  • SIMPLYNODE
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE

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
79.135.160.0/198,192PL-BSMBTK-20100107Bialogardzka Spoldzielnia Mieszkaniowa (ORG-BSM2-RIPE) · PLALLOCATED PAJan 7, 2010abuse@btk.net.pl
└ 79.135.160.0/2664BSMBialogardzka Spoldzielnia Mieszkaniowa (ORG-BSM2-RIPE) · PLASSIGNED PAJan 8, 2010abuse@btk.net.pl
└ 79.135.160.64 - 79.135.160.255192BSMBialogardzka Spoldzielnia Mieszkaniowa (ORG-BSM2-RIPE) · PLASSIGNED PAJan 8, 2010abuse@btk.net.pl
└ 79.135.161.0 - 79.135.176.2554,096BSMBialogardzka Spoldzielnia Mieszkaniowa (ORG-BSM2-RIPE) · PLASSIGNED PAAug 5, 2010abuse@btk.net.pl
└ 79.135.177.0 - 79.135.186.2552,560BSMBialogardzka Spoldzielnia Mieszkaniowa - Broadband UsersASSIGNED PAJul 22, 2013abuse@btk.net.pl
via PL-BSMBTK-20100107
└ 79.135.187.0 - 79.135.191.2551,280BSMBialogardzka Spoldzielnia Mieszkaniowa - Broadband UsersASSIGNED PANov 30, 2015abuse@btk.net.pl
via PL-BSMBTK-20100107

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
Dec 2007
Current origin since
Jun 2011 · 15 yr
Origin networks
4
Last change of origin
Jun 2011
Recorded history

History

Handoffs
3