asn.dev

Observed topology

AS200759 FLOW Switzerland

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS200759: 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 LLCTransitIPv4190
AS25091IP-Max SAUnclassifiedIPv4 IPv6136
AS13030Init7 (Switzerland) Ltd.HostingIPv425
AS3303Swisscom (Schweiz) AGResidentialIPv45
AS24482SG.GSHostingIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS202411Flow Swiss AGUnclassifiedIPv465
AS214552Flow Swiss AGUnclassifiedIPv465
AS203892Flow Swiss AGUnclassifiedIPv463
AS202240Innflow AGUnclassifiedIPv4 IPv654

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4354
AS25091IP-Max SAUnclassifiedIPv4 IPv6194
AS202411Flow Swiss AGUnclassifiedIPv465
AS214552Flow Swiss AGUnclassifiedIPv465
AS203892Flow Swiss AGUnclassifiedIPv463
AS202240Innflow AGUnclassifiedIPv4 IPv654
AS13030Init7 (Switzerland) Ltd.HostingIPv439
AS3303Swisscom (Schweiz) AGResidentialIPv48
AS24482SG.GSHostingIPv48
AS6730Sunrise GmbHMobileIPv44

All 11 adjacent →

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.