Data as of Nov 11, 2026

5.149.112.0/24

1 residential-proxy exit · 30 days

Luxnetwork S.A.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business
91% of it

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
12
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

47 observations

Proxy providers listing exits

  • 9Proxy
  • BottingTools
  • CatProxies
  • Geonode
  • HideProxy
  • InfiniteProxies
  • LudaxProxy
  • NextProxy
  • ProxiesVision
  • ProxyGeo
  • RealProxy
  • 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
5.149.112.0/212,048LU-LUXNETWORK-20120716Luxnetwork S.A. (ORG-LS105-RIPE) · LUALLOCATED PAJul 16, 2012abuse@luxnetwork.eu
└ 5.149.112.0/2816CA160E19B12CA160E19B12ASSIGNED PAJun 30, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.16/298CF789F32L72CF789F32L72ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.24/304CS171E25L12CS171E25L12ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.28/304CS171E25L13CS171E25L13ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.32/298CB537A85V67CB537A85V67ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.40/304CB537A85T36CB537A85T36ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.44/304CE177A02C87CE177A02C87ASSIGNED PADec 15, 2015abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.48/298CV350A03N67CV350A03N67ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.56/304CB428Z83N22CB428Z83N22ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.60/304CB540E21R10CB540E21R10ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.64/298CS171E25L12CS171E25L12ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.72/298CS171E25L13CS171E25L13ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.88/298CB540E02F48CB540E02F48ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.96/304CS156A33P40CS156A33P40ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.100/304CT338Z84F41CT338Z84F41ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.104/304CB139A19B14CB139A19B14ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.112/298CT358A01V22CT358A01V22ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.120/298CS169E21R70CS169E21R70ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.128/304CB372E08S01CB372E08S01ASSIGNED PAApr 22, 2015abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.132/304CB372E08D05CB372E08D05ASSIGNED PAApr 22, 2015abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.136/304CB189D22N88CB189D22N88ASSIGNED PAApr 22, 2015abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.140/304CS160B71D40CS160B71D40ASSIGNED PAApr 22, 2015abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.144/304LN999T49R93LN999T49R93ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.148/304CA401D29F01CA401D29F01ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.152/298CG258A20U77CG258A20U77ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.160/298CT280A04H44CT280A04H44ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.168/298CB341D25I30CB341D25I30ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.176/2816CB407T28D06CB407T28D06ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.192/304CB458T20M30CB458T20M30ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.196/304CT197N44N12CT197N44N12ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.200/298LN999D08C16LN999D08C16ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.208/2816CT184E71S03CT184E71S03ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.224/298CS158D24I91CS158D24I91ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.232/298CS177E44C05CS177E44C05ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.244/312CB210M71B20CB210M71B20ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716
└ 5.149.112.246/312CB210M71B20CB210M71B20ASSIGNED PAJul 8, 2025abuse@luxnetwork.eu
via LU-LUXNETWORK-20120716

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Business23291%36
Internet provider249.4%4

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Nov 2015
Current origin since
May 2019 · 7.5 yr
Origin networks
2
Last change of origin
May 2019
Recorded history

History

Handoffs
1