asn.dev

Observed topology

AS34572 HELIANTIS-AS

Unclassified RIPE

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS34572: 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
AS39801France IX Services SASUUnclassifiedIPv4275
AS6461Zayo BandwidthTransitIPv4 IPv6176
AS6939Hurricane Electric LLCTransitIPv4 IPv684
AS31167AXIONE S.A.S.UnclassifiedIPv460
AS33891Core-Backbone GmbHHostingIPv48
AS24482SG.GSHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv66
AS12779IT.Gate S.p.A.UnclassifiedIPv45
AS20766Association "Gitoyen"UnclassifiedIPv45

All 17 upstreams →

Transit

Downstream networks

inferred

Networks for which AS34572 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 17

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

ASNetworkTypeFamiliesPaths seen
AS39801France IX Services SASUUnclassifiedIPv4275
AS6461Zayo BandwidthTransitIPv4 IPv6176
AS6939Hurricane Electric LLCTransitIPv4 IPv684
AS31167AXIONE S.A.S.UnclassifiedIPv460
AS33891Core-Backbone GmbHHostingIPv48
AS24482SG.GSHostingIPv4 IPv66
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv66
AS12779IT.Gate S.p.A.UnclassifiedIPv45
AS20766Association "Gitoyen"UnclassifiedIPv45

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