AS39180 LASOTEL LASOTEL SAS
π«π·Org handle: ORG-LS331-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
13total
11 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)15,872
Announced (BGP)16,896
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)1.5Γ10Β²βΉ
Prefix Limit (IPv4)
50
Prefix Limit (IPv6)
10
Country
π«π· FRRIR
RIPE NCCStatus
allocated
Allocated
2005-12-29
Announced Prefixes
(BGP)13|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
185.60.8.0/24MOAS | No ROA | - | 2026-10-11 |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
1-10 of 13
1 / 2
Allocated Prefixes
(RIR)8Prefix | Country | RIR | Status |
|---|---|---|---|
| 37.148.240.0/21 | π«π· FR | RIPENCC | allocated |
| 81.18.176.0/20 | π«π· FR | RIPENCC | allocated |
| 93.191.40.0/21 | π«π· FR | RIPENCC | allocated |
| 178.18.48.0/20 | π«π· FR | RIPENCC | allocated |
| 185.153.244.0/22 | π«π· FR | RIPENCC | allocated |
| 185.191.203.0/24 | πΈπ¬ SG | RIPE | assigned |
| 188.93.40.0/21 | π«π· FR | RIPENCC | allocated |
| 195.13.34.0/24 | π«π· FR | RIPENCC | assigned |
All 13 announced prefixes of AS39180 β
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS39180 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (10)
Networks whose own prefixes AS39180 passes on: usually its customers.
- AS201479BULLGREOSI Bull SAS6
- AS201900OLGroupe EAGLE FOOTBALL GROUP5
- AS202328AOCTEL ATELIER OLIVIER CHARNAY TELECOM SAS5
- AS60502ONESYSTEM 01 SYSTEM2
- AS51458GLECCCL GL Events CITE/CENTRE DE CONGRES/LYON1
- AS57004SOITEC1
- AS200621NetEntreprise Feyzin Ctre Reg Traitement Information Lyon1
- AS202546BLUECOM SAS1
- AS203500ABEILLE SARL1
- AS209760Actasa ACTA SAS1
ASPA
No ASPA
Abuse Contact
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS39180 should publish an ASPA object
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/39180Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/39180" | jq