asn.dev

Observed topology

AS8469 PIRONETNDH-AS CANCOM Managed Services GmbH

Hosting RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS8469: 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
AS13237euNetworks GmbHUnclassifiedIPv4 IPv6242
AS3356Level 3 Parent, LLCTransitIPv4 IPv6225
AS6939Hurricane Electric LLCTransitIPv4 IPv690
AS3320Deutsche Telekom AGMobileIPv4 IPv660
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv637
AS33891Core-Backbone GmbHHostingIPv422
AS24482SG.GSHostingIPv4 IPv613
AS34019Hivane AssociationUnclassifiedIPv4 IPv613
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv613
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv613

All 20 upstreams →

Transit

Downstream networks

inferred

Networks for which AS8469 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 AS8469 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS13237euNetworks GmbHUnclassifiedIPv4 IPv6242
AS3356Level 3 Parent, LLCTransitIPv4 IPv6225
AS6939Hurricane Electric LLCTransitIPv4 IPv690
AS3320Deutsche Telekom AGMobileIPv4 IPv660
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv637
AS33891Core-Backbone GmbHHostingIPv422
AS24482SG.GSHostingIPv4 IPv613
AS34019Hivane AssociationUnclassifiedIPv4 IPv613
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv613
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv613

All 20 adjacent →

Provenance

Where this comes from

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