asn.dev

Observed topology

AS60427 SYSTEM-NET-AS System-Net Sas

Residential RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS60427: 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
AS30781Free Pro SASHostingIPv4205
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv6126
AS6939Hurricane Electric LLCTransitIPv4 IPv668
AS174Cogent Communications, LLCTransitIPv4 IPv664
AS34549meerfarbig GmbH & Co. KGHostingIPv421
AS24482SG.GSHostingIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv68
AS20766Association "Gitoyen"UnclassifiedIPv47
AS3215Orange S.A.MobileIPv44
AS12779IT.Gate S.p.A.UnclassifiedIPv44

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS203770Matooma SASUnclassifiedIPv42

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS30781Free Pro SASHostingIPv4205
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv6126
AS6939Hurricane Electric LLCTransitIPv4 IPv669
AS174Cogent Communications, LLCTransitIPv4 IPv664
AS34549meerfarbig GmbH & Co. KGHostingIPv421
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv69
AS24482SG.GSHostingIPv4 IPv68
AS20766Association "Gitoyen"UnclassifiedIPv47
AS3215Orange S.A.MobileIPv44
AS12779IT.Gate S.p.A.UnclassifiedIPv44

All 14 adjacent →

Provenance

Where this comes from

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