asn.dev

Observed topology

AS47160 MOJI MOJI SAS

Residential RIPE

Upstreams 1 carry this network
Downstreams 18 this network carries
Adjacent (IPv4) 19
Adjacent (IPv6) 16
Upstream graph Who carries AS47160, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS47160 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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.

ASNetworkTypeFamiliesPaths seen
AS62000SERVERD SASHostingIPv4 IPv6807

Transit

Downstream networks

All 18

Networks for which AS47160 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS205669Association ResElUnclassifiedIPv4 IPv6367
AS203500ABEILLE SARLResidentialIPv4 IPv6286
AS39421Sapinet SASUnclassifiedIPv4 IPv6210
AS213873MOJI SASUnclassifiedIPv4 IPv6156
AS48813Enix SASUnclassifiedIPv4 IPv6140
AS203062Alexandre RouxUnclassifiedIPv4 IPv6106
AS214390Wojtek SASU, trading as GofileHostingIPv4 IPv695
AS212949Mistral AI SASUnclassifiedIPv4 IPv691
AS213095Exaion SASUnclassifiedIPv4 IPv670
AS205259Substrate HD SASUnclassifiedIPv460

All 18 downstreams →

Adjacency

Adjacent networks

All 19

Every AS seen directly next to AS47160 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS62000SERVERD SASHostingIPv4 IPv62,813
AS205669Association ResElUnclassifiedIPv4 IPv6367
AS203500ABEILLE SARLResidentialIPv4 IPv6349
AS39421Sapinet SASUnclassifiedIPv4 IPv6237
AS48813Enix SASUnclassifiedIPv4 IPv6166
AS213873MOJI SASUnclassifiedIPv4 IPv6156
AS203062Alexandre RouxUnclassifiedIPv4 IPv6106
AS214390Wojtek SASU, trading as GofileHostingIPv4 IPv695
AS212949Mistral AI SASUnclassifiedIPv4 IPv691
AS203698MOJI SASUnclassifiedIPv4 IPv674

All 19 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.