Observed topology
AS39180 LASOTEL
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS39180: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS29075 | IELO-LIAZO SERVICES SAS | Unclassified | IPv4 IPv6 | 275 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 176 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 72 |
| AS4455 | IX Reach Ltd | Unclassified | IPv4 | 18 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 11 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 11 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 11 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 11 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 11 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 9 |
Transit
Downstream networks
Networks for which AS39180 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS202328 | ATELIER OLIVIER CHARNAY TELECOM SAS | Unclassified | IPv4 | 230 |
| AS201900 | EAGLE FOOTBALL GROUP SA | Unclassified | IPv4 | 215 |
| AS60502 | 01 SYSTEM SRL | Residential | IPv4 | 120 |
| AS201479 | Bull SAS | Unclassified | IPv4 | 116 |
| AS57004 | Soitec SA | Unclassified | IPv4 | 60 |
| AS202546 | Bluecom SAS | Unclassified | IPv4 | 59 |
| AS48140 | Agence Centrale Des Organismes De Securite Sociale | Unclassified | IPv4 | 51 |
| AS35009 | SOWILO NETWORK SARL | Unclassified | IPv4 | 33 |
| AS60902 | ACCESS HEBERGEMENT s.a.r.l. | Unclassified | IPv4 | 31 |
| AS201425 | Ctre Reg Traitement Information Lyon | Unclassified | IPv4 | 18 |
Adjacency
Adjacent networks
Every AS seen directly next to AS39180 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 670 |
| AS29075 | IELO-LIAZO SERVICES SAS | Unclassified | IPv4 IPv6 | 296 |
| AS202328 | ATELIER OLIVIER CHARNAY TELECOM SAS | Unclassified | IPv4 | 230 |
| AS201900 | EAGLE FOOTBALL GROUP SA | Unclassified | IPv4 | 215 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 168 |
| AS60502 | 01 SYSTEM SRL | Residential | IPv4 | 120 |
| AS201479 | Bull SAS | Unclassified | IPv4 | 116 |
| AS57004 | Soitec SA | Unclassified | IPv4 | 60 |
| AS202546 | Bluecom SAS | Unclassified | IPv4 | 59 |
| AS48140 | Agence Centrale Des Organismes De Securite Sociale | Unclassified | IPv4 | 51 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-20 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.16M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.