asn.dev

Observed topology

AS60816 INTERACTION-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS60816: 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
AS202399Stowarzyszenie Artystyczno Medialne Art MediaUnclassifiedIPv453
AS50607Stowarzyszenie e-PoludnieUnclassifiedIPv47
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS202399Stowarzyszenie Artystyczno Medialne Art MediaUnclassifiedIPv440

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS202399Stowarzyszenie Artystyczno Medialne Art MediaUnclassifiedIPv493
AS50607Stowarzyszenie e-PoludnieUnclassifiedIPv442
AS201054Stowarzyszenie e-PoludnieUnclassifiedIPv46

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.