asn.dev

Observed topology

AS216096 SECUREPEAK

Unclassified RIPE

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

Transit

Upstream networks

All 24

Networks observed carrying traffic for AS216096: 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
AS34927iFog GmbHHostingIPv4 IPv6147
AS34872Sarah Rossius trading as Servperso SystemsHostingIPv4 IPv653
AS1299Arelion Sweden ABTransitIPv4 IPv639
AS3257GTT Communications Inc.TransitIPv4 IPv623
AS6939Hurricane Electric LLCTransitIPv421
AS23961Misaka Network, Inc.UnclassifiedIPv4 IPv620
AS58057Securebit AGUnclassifiedIPv4 IPv620
AS50304Blix Solutions ASUnclassifiedIPv4 IPv613
AS24482SG.GSHostingIPv4 IPv68
AS37989DCS1 Pte. Ltd.HostingIPv48

All 24 upstreams →

Transit

Downstream networks

inferred

Networks for which AS216096 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 24

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

ASNetworkTypeFamiliesPaths seen
AS34927iFog GmbHHostingIPv4 IPv6147
AS34872Sarah Rossius trading as Servperso SystemsHostingIPv4 IPv653
AS1299Arelion Sweden ABTransitIPv4 IPv639
AS3257GTT Communications Inc.TransitIPv4 IPv623
AS6939Hurricane Electric LLCTransitIPv421
AS23961Misaka Network, Inc.UnclassifiedIPv4 IPv620
AS58057Securebit AGUnclassifiedIPv4 IPv620
AS50304Blix Solutions ASUnclassifiedIPv4 IPv613
AS24482SG.GSHostingIPv4 IPv68
AS37989DCS1 Pte. Ltd.HostingIPv48

All 24 adjacent →

Provenance

Where this comes from

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