asn.dev

Observed topology

AS196954 epcan Epcan GmbH

Unclassified RIPE

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS196954: 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 IPv6451
AS1299Arelion Sweden ABTransitIPv4 IPv676
AS24961WIIT AGHostingIPv4 IPv673
AS33891Core-Backbone GmbHHostingIPv4 IPv650
AS5405Inter.link GmbHUnclassifiedIPv4 IPv640
AS24482SG.GSHostingIPv4 IPv613
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv613
AS212024Marc SchmittUnclassifiedIPv4 IPv613
AS213241TECHIT.BE SRLResidentialIPv4 IPv613
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv612

All 19 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49034Laudert GmbH + Co. KGUnclassifiedIPv4 IPv6166
AS214239ambiFOX GmbHUnclassifiedIPv465

Adjacency

Adjacent networks

All 21

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6596
AS49034Laudert GmbH + Co. KGUnclassifiedIPv4 IPv6166
AS1299Arelion Sweden ABTransitIPv4 IPv697
AS24961WIIT AGHostingIPv4 IPv686
AS214239ambiFOX GmbHUnclassifiedIPv465
AS33891Core-Backbone GmbHHostingIPv4 IPv660
AS5405Inter.link GmbHUnclassifiedIPv4 IPv648
AS24482SG.GSHostingIPv4 IPv617
AS212024Marc SchmittUnclassifiedIPv4 IPv617
AS213241TECHIT.BE SRLResidentialIPv4 IPv617

All 21 adjacent →

Provenance

Where this comes from

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