asn.dev

Observed topology

AS51978 WEMACOM International Backbone WEMACOM Telekommunikation GmbH

Residential RIPE

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

Transit

Upstream networks

All 29

Networks observed carrying traffic for AS51978: 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
AS1299Arelion Sweden ABTransitIPv4 IPv680
AS2914NTT America, Inc.TransitIPv4 IPv672
AS6939Hurricane Electric LLCTransitIPv4 IPv667
AS3356Level 3 Parent, LLCTransitIPv456
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv623
AS6461Zayo BandwidthTransitIPv414
AS1836green.ch AGResidentialIPv4 IPv68
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv68
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv68

All 29 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS198726Wemaconnect GmbHResidentialIPv4 IPv6425

Adjacency

Adjacent networks

All 31

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

ASNetworkTypeFamiliesPaths seen
AS198726Wemaconnect GmbHResidentialIPv4 IPv6922
AS2914NTT America, Inc.TransitIPv4 IPv6470
AS1299Arelion Sweden ABTransitIPv4 IPv6358
AS3356Level 3 Parent, LLCTransitIPv4 IPv6290
AS6939Hurricane Electric LLCTransitIPv4 IPv667
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv623
AS6461Zayo BandwidthTransitIPv414
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv611
AS1103SURF B.V.UnclassifiedIPv49
AS1836green.ch AGResidentialIPv4 IPv68

All 31 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 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.