asn.dev

Observed topology

AS1120 ACOnet_Services - ACONET

Unclassified RIPE Non-Profit

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS1120: 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 IPv652
AS9002RETN LimitedUnclassifiedIPv4 IPv618
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv66
AS33891Core-Backbone GmbHHostingIPv44
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64
AS13030Init7 (Switzerland) Ltd.HostingIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS31529DENIC eGUnclassifiedIPv48
AS35052ACONETUnclassifiedIPv47
AS14650Nucleo de Inf. e Coord. do Ponto BR - NIC.BRUnclassifiedIPv46
AS52306NIC ChileUnclassifiedIPv41

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv652
AS9002RETN LimitedUnclassifiedIPv4 IPv621
AS1853ACONETUnclassifiedIPv415
AS31529DENIC eGUnclassifiedIPv48
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv67
AS35052ACONETUnclassifiedIPv47
AS14650Nucleo de Inf. e Coord. do Ponto BR - NIC.BRUnclassifiedIPv46
AS33891Core-Backbone GmbHHostingIPv46
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv64
AS13030Init7 (Switzerland) Ltd.HostingIPv62

All 12 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.