asn.dev

Observed topology

AS215859 HETZNER-CLOUD4-AS

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS215859: 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 LLCTransitIPv4987
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv684
AS38001NewMedia Express Pte LtdHostingIPv4 IPv684
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv483
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv683
AS18106Viewqwest Pte LtdResidentialIPv4 IPv639
AS24482SG.GSHostingIPv4 IPv632
AS2914NTT America, Inc.TransitIPv4 IPv622
AS1299Arelion Sweden ABTransitIPv43
AS61292Blix Group ASUnclassifiedIPv61

Transit

Downstream networks

inferred

Networks for which AS215859 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4987
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv684
AS38001NewMedia Express Pte LtdHostingIPv4 IPv684
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv483
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv683
AS18106Viewqwest Pte LtdResidentialIPv4 IPv639
AS24482SG.GSHostingIPv4 IPv632
AS2914NTT America, Inc.TransitIPv4 IPv622
AS1299Arelion Sweden ABTransitIPv43
AS61292Blix Group ASUnclassifiedIPv61

Provenance

Where this comes from

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