asn.dev

Observed topology

AS64457 PIPEHOST-AS Matteo Fruhwald trading as PipeHost e.U.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS64457: 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
AS215120Evolus IT Solutions GmbHUnclassifiedIPv4152
AS49581Ferdinand Zink trading as Tube-HostingHostingIPv489
AS6939Hurricane Electric LLCTransitIPv4 IPv658
AS51396Pfcloud UG (haftungsbeschrankt)HostingIPv637
AS49592Pipe Networks GmbHUnclassifiedIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS51396Pfcloud UG (haftungsbeschrankt)HostingIPv6324
AS199550HIRAGI LTDUnclassifiedIPv4182
AS203156Relayify LLCUnclassifiedIPv4116

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6426
AS215120Evolus IT Solutions GmbHUnclassifiedIPv4406
AS51396Pfcloud UG (haftungsbeschrankt)HostingIPv6361
AS199550HIRAGI LTDUnclassifiedIPv4182
AS203156Relayify LLCUnclassifiedIPv4116
AS49581Ferdinand Zink trading as Tube-HostingHostingIPv489
AS49592Pipe Networks GmbHUnclassifiedIPv48

Provenance

Where this comes from

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