Observed topology
AS47160 MOJI MOJI SAS
Residential RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS47160: 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 |
|---|---|---|---|---|
| AS62000 | SERVERD SAS | Hosting | IPv4 IPv6 | 807 |
Transit
Downstream networks
Networks for which AS47160 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS205669 | Association ResEl | Unclassified | IPv4 IPv6 | 381 |
| AS203500 | ABEILLE SARL | Residential | IPv4 IPv6 | 276 |
| AS39421 | Sapinet SAS | Unclassified | IPv4 IPv6 | 224 |
| AS48813 | Enix SAS | Unclassified | IPv4 IPv6 | 172 |
| AS213873 | MOJI SAS | Unclassified | IPv4 IPv6 | 156 |
| AS203062 | Alexandre Roux | Unclassified | IPv4 IPv6 | 153 |
| AS215142 | Association By-Hoster | Unclassified | IPv4 IPv6 | 139 |
| AS214390 | Wojtek SASU, trading as Gofile | Hosting | IPv4 IPv6 | 95 |
| AS213095 | Exaion SAS | Unclassified | IPv4 IPv6 | 92 |
| AS212949 | Mistral AI SAS | Unclassified | IPv4 IPv6 | 67 |
Adjacency
Adjacent networks
Every AS seen directly next to AS47160 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS62000 | SERVERD SAS | Hosting | IPv4 IPv6 | 3,058 |
| AS205669 | Association ResEl | Unclassified | IPv4 IPv6 | 381 |
| AS203500 | ABEILLE SARL | Residential | IPv4 IPv6 | 342 |
| AS39421 | Sapinet SAS | Unclassified | IPv4 IPv6 | 240 |
| AS48813 | Enix SAS | Unclassified | IPv4 IPv6 | 204 |
| AS213873 | MOJI SAS | Unclassified | IPv4 IPv6 | 156 |
| AS203062 | Alexandre Roux | Unclassified | IPv4 IPv6 | 153 |
| AS215142 | Association By-Hoster | Unclassified | IPv4 IPv6 | 139 |
| AS214390 | Wojtek SASU, trading as Gofile | Hosting | IPv4 IPv6 | 95 |
| AS203698 | MOJI SAS | Unclassified | IPv4 IPv6 | 92 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-05 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 73.57M 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.