asn.dev

Observed topology

AS29413 KOMRO-AS Komro Telekommunikations GmbH

Residential RIPE

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS29413: 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 IPv6366
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6248
AS6939Hurricane Electric LLCTransitIPv4 IPv6146
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv644
AS24482SG.GSHostingIPv4 IPv616
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv616
AS212024Marc SchmittUnclassifiedIPv4 IPv616
AS6797GlobalConnect ABUnclassifiedIPv414
AS20485Joint Stock Company TransTeleComUnclassifiedIPv414
AS34019Hivane AssociationUnclassifiedIPv414

All 14 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49696ROCT GmbHUnclassifiedIPv4 IPv660

Adjacency

Adjacent networks

All 16

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6378
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6262
AS6939Hurricane Electric LLCTransitIPv4 IPv6167
AS49696ROCT GmbHUnclassifiedIPv4 IPv660
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv648
AS212024Marc SchmittUnclassifiedIPv4 IPv618
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv617
AS24482SG.GSHostingIPv4 IPv616
AS20485Joint Stock Company TransTeleComUnclassifiedIPv415
AS6797GlobalConnect ABUnclassifiedIPv414

All 16 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.