asn.dev

Observed topology

AS206141 DVV-GMBH-AS

Unclassified ARIN NSP

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS206141: 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 IPv688
AS6939Hurricane Electric LLCTransitIPv4 IPv642
AS34309Link11 GmbHUnclassifiedIPv4 IPv624
AS3320Deutsche Telekom AGMobileIPv4 IPv617
AS58243TELE AGUnclassifiedIPv616
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv611
AS24482SG.GSHostingIPv4 IPv65
AS34019Hivane AssociationUnclassifiedIPv4 IPv65
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv65
AS212024Marc SchmittUnclassifiedIPv4 IPv65

All 20 upstreams →

Transit

Downstream networks

inferred

Networks for which AS206141 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 20

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv688
AS6939Hurricane Electric LLCTransitIPv4 IPv642
AS34309Link11 GmbHUnclassifiedIPv4 IPv624
AS3320Deutsche Telekom AGMobileIPv4 IPv617
AS58243TELE AGUnclassifiedIPv616
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv611
AS24482SG.GSHostingIPv4 IPv65
AS34019Hivane AssociationUnclassifiedIPv4 IPv65
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv65
AS212024Marc SchmittUnclassifiedIPv4 IPv65

All 20 adjacent →

Provenance

Where this comes from

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