Data as of Nov 12, 2026

176.32.34.0/24

1 residential-proxy exit · 30 days

LLC Baxet

Announcement
this exact prefix
No RPKI
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
19
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

40 observations

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • EZProxies
  • GSocks
  • Geonix
  • IPFly
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxio
  • Proxy-Seller
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalExclusive
IPv4 market

Path

1 · Holder
LLC Baxet
record created May 23, 2011
2 · Leased from
its owner, directly
3 · Announced by
AS51659 LLC Baxet
since Oct 2025 · 13 mo ago
4 · Use
Hosting

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

176.32.34.0/24

From the registry to its use

  1. May 23, 2011
    Registry record
    LLC Baxet
    ALLOCATED PA
    176.32.32.0/21
  2. Dec 8, 2017– Dec 19, 2017
    Announced
    AS56694 LLC Smart Ape
    Hosting
  3. Jan 4, 2018
    Route object
    AS51659 LLC Baxet
    RIPE route object for AS51659 LLC Baxet, maintainer BX-NOC
  4. May 13, 2018– Nov 30, 2023
    Announced
    AS51659 LLC Baxet
    Hosting
  5. Dec 13, 2023– Jul 3, 2024
    Announced
    AS49392 LLC Baxet
    Hosting
  6. May 17, 2025
    Route object
    AS49392 LLC Baxet
    RIPE route object for AS49392 LLC Baxet, maintainer BX-NOC
  7. Oct 3, 2025– today
    Announced
    AS51659 LLC Baxet
    Hosting
  8. today
    Leased from
    InterLIR
    Lessor

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
176.32.32.0/212,048RU-BXTGROUP-20110523LLC Baxet (ORG-LB12-RIPE) · RUALLOCATED PAMay 23, 2011noc@baxet.ru
└ 176.32.34.0/24256BX-NETWORKunknownASSIGNED PADec 13, 2017noc@baxet.ru
via RU-BXTGROUP-20110523

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
Reactivated
First seen
Dec 2017
Current origin since
Oct 2025 · 1.1 yr
Origin networks
3
Last change of origin
Oct 2025
Recorded history

History

Handoffs
3