asn.dev

Observed topology

AS216039 EDGESEC-AS

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS216039: 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
AS137409GSL Networks Pty LTDUnclassifiedIPv4366
AS49581Ferdinand Zink trading as Tube-HostingHostingIPv4 IPv6277
AS219236Wolf Girls LimitedUnclassifiedIPv4180
AS214309Aurorix Gaming Solutions LimitedHostingIPv634
AS35598INETCOM CARRIER LLCUnclassifiedIPv629
AS62255BiMajLink d.o.o.UnclassifiedIPv68

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS219227VANISH CLOUD LTDUnclassifiedIPv454
AS214309Aurorix Gaming Solutions LimitedHostingIPv424

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS137409GSL Networks Pty LTDUnclassifiedIPv4420
AS49581Ferdinand Zink trading as Tube-HostingHostingIPv4 IPv6277
AS219236Wolf Girls LimitedUnclassifiedIPv4204
AS214309Aurorix Gaming Solutions LimitedHostingIPv4 IPv658
AS219227VANISH CLOUD LTDUnclassifiedIPv454
AS35598INETCOM CARRIER LLCUnclassifiedIPv629
AS62255BiMajLink d.o.o.UnclassifiedIPv68

Provenance

Where this comes from

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