asn.dev

Observed topology

AS29655 TRENKA Trenka Informatik AG

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS29655: 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 IPv6126
AS3257GTT Communications Inc.TransitIPv4106
AS6939Hurricane Electric LLCTransitIPv4 IPv679
AS33891Core-Backbone GmbHHostingIPv410
AS1836green.ch AGResidentialIPv4 IPv67
AS24482SG.GSHostingIPv4 IPv67
AS34019Hivane AssociationUnclassifiedIPv4 IPv67
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv67
AS9002RETN LimitedUnclassifiedIPv66
AS13030Init7 (Switzerland) Ltd.HostingIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS60016Fiberstream 87 AGUnclassifiedIPv4638

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS60016Fiberstream 87 AGUnclassifiedIPv4638
AS3257GTT Communications Inc.TransitIPv4468
AS1299Arelion Sweden ABTransitIPv4 IPv6226
AS6939Hurricane Electric LLCTransitIPv4 IPv6189
AS33891Core-Backbone GmbHHostingIPv432
AS1836green.ch AGResidentialIPv4 IPv618
AS24482SG.GSHostingIPv4 IPv618
AS34019Hivane AssociationUnclassifiedIPv4 IPv618
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv618
AS9002RETN LimitedUnclassifiedIPv66

All 11 adjacent →

Provenance

Where this comes from

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