asn.dev

Observed topology

AS60989 SINERGIA

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS60989: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6168
AS41327Fiber Telecom S.p.A.ResidentialIPv4 IPv6166
AS174Cogent Communications, LLCTransitIPv4 IPv659
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv625
AS24482SG.GSHostingIPv4 IPv616
AS59919Brainbox S.r.l.ResidentialIPv414
AS8218Zayo Infrastructure France SAUnclassifiedIPv410
AS31543myNet GmbHResidentialIPv410
AS196959NAMEX CONSORZIOUnclassifiedIPv410
AS29632Netassist International EOODUnclassifiedIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209076Vayu S.r.lUnclassifiedIPv633

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6182
AS41327Fiber Telecom S.p.A.ResidentialIPv4 IPv6166
AS174Cogent Communications, LLCTransitIPv4 IPv659
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv639
AS209076Vayu S.r.lUnclassifiedIPv633
AS24482SG.GSHostingIPv4 IPv617
AS59919Brainbox S.r.l.ResidentialIPv414
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv611
AS31543myNet GmbHResidentialIPv4 IPv611
AS196959NAMEX CONSORZIOUnclassifiedIPv410

All 11 adjacent →

Provenance

Where this comes from

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