asn.dev

Observed topology

AS12355 HAMCOM-DE Hamm, Germany

Residential RIPE

Upstreams 31 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 29
Adjacent (IPv6) 15
Upstream graph Who carries AS12355, and who carries them, drawn as a map up to the transit-free core. 4 exchanges Where AS12355 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 31

Networks observed carrying traffic for AS12355: 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 IPv6308
AS50629LWLcom GmbHUnclassifiedIPv4 IPv6109
AS2914NTT America, Inc.TransitIPv4 IPv682
AS24482SG.GSHostingIPv4 IPv626
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv626
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv620
AS42708Glesys ABUnclassifiedIPv4 IPv620
AS48185team.blue NVUnclassifiedIPv4 IPv620
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv620
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv620

All 31 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 31

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6308
AS50629LWLcom GmbHUnclassifiedIPv4 IPv6109
AS2914NTT America, Inc.TransitIPv4 IPv682
AS24482SG.GSHostingIPv4 IPv626
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv626
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv620
AS42708Glesys ABUnclassifiedIPv4 IPv620
AS48185team.blue NVUnclassifiedIPv4 IPv620
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv620
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv620

All 31 adjacent →

Provenance

Where this comes from

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