asn.dev

Observed topology

AS50469 HESSENKOM-DE Peer Kohlstetter trading as Hessenkom GmbH & Co. KG

Unclassified RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS50469: 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 IPv61,163
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6501
AS9002RETN LimitedUnclassifiedIPv4 IPv6117
AS9136Wobcom GmbHResidentialIPv4 IPv6107
AS34549meerfarbig GmbH & Co. KGHostingIPv471
AS3320Deutsche Telekom AGMobileIPv449
AS8551Bezeq International Ltd.UnclassifiedIPv425
AS24482SG.GSHostingIPv425
AS37100SEACOM LimitedUnclassifiedIPv425
AS212024Marc SchmittUnclassifiedIPv425

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208968Avacon Connect GmbHUnclassifiedIPv4 IPv6519
AS206480Jens LinkUnclassifiedIPv633

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,414
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6717
AS208968Avacon Connect GmbHUnclassifiedIPv4 IPv6519
AS9002RETN LimitedUnclassifiedIPv4 IPv6150
AS9136Wobcom GmbHResidentialIPv4 IPv6107
AS3320Deutsche Telekom AGMobileIPv4101
AS34549meerfarbig GmbH & Co. KGHostingIPv471
AS206480Jens LinkUnclassifiedIPv633
AS8551Bezeq International Ltd.UnclassifiedIPv425
AS24482SG.GSHostingIPv425

All 15 adjacent →

Provenance

Where this comes from

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