Data as of Nov 12, 2026

178.18.48.0/20

1 residential-proxy exit · 30 days

Lasotel SAS

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

Residential-proxy exits

Proxy exits
1
0.02% of its addresses · 30 days
Spread
1 of 16
/24s with at least one exit
Providers
2
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

44 observations

Proxy providers listing exits

  • RainProxy
  • Shifter

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
178.18.48.0/204,096FR-LASOTEL-20100409Lasotel SAS (ORG-LS331-RIPE) · FRALLOCATED PAApr 9, 2010abuse@lasotel.net
└ 178.18.50.0/24256LASOTELCustomers Links xDSLASSIGNED PADec 4, 2010abuse@lasotel.net
via FR-LASOTEL-20100409
└ 178.18.51.0/24256LASOTELLasotel SAS (ORG-LS331-RIPE) · FRASSIGNED PADec 4, 2010abuse@lasotel.net
└ 178.18.57.0/24256K-NETLasotel SAS (ORG-LS331-RIPE) · FRASSIGNED PAJul 6, 2010abuse@lasotel.net
└ 178.18.63.0/24256K-NETLasotel SAS (ORG-LS331-RIPE) · FRASSIGNED PADec 7, 2010abuse@lasotel.net

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
Apr 2010
Current origin since
Apr 2010 · 17 yr
Origin networks
1