asn.dev

Observed topology

AS61174 GLATTWERK Usterstrasse 111

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS61174: 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
AS174Cogent Communications, LLCTransitIPv4 IPv6126
AS8220COLT Technology Services Group LimitedHostingIPv4 IPv6110
AS6939Hurricane Electric LLCTransitIPv4 IPv666
AS1836green.ch AGResidentialIPv4 IPv66
AS24482SG.GSHostingIPv4 IPv66
AS34019Hivane AssociationUnclassifiedIPv4 IPv66
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv66
AS9002RETN LimitedUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS210231Sysdex AGUnclassifiedIPv4 IPv615

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6141
AS8220COLT Technology Services Group LimitedHostingIPv4 IPv6110
AS6939Hurricane Electric LLCTransitIPv4 IPv666
AS210231Sysdex AGUnclassifiedIPv4 IPv615
AS1836green.ch AGResidentialIPv4 IPv66
AS24482SG.GSHostingIPv4 IPv66
AS34019Hivane AssociationUnclassifiedIPv4 IPv66
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv66
AS9002RETN LimitedUnclassifiedIPv61

Provenance

Where this comes from

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