asn.dev

Observed topology

AS13684 ASN-MEDTRONIC-1

Unclassified ARIN

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS13684: 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
AS702Verizon BusinessUnclassifiedIPv4508
AS3356Level 3 Parent, LLCTransitIPv4 IPv6255
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4199
AS209CenturyLink Communications, LLCResidentialIPv4173
AS39686Eurofiber Nederland BVResidentialIPv4 IPv6163
AS703Verizon BusinessUnclassifiedIPv4151
AS2516KDDI CORPORATIONMobileIPv474
AS18229CtrlSHostingIPv459
AS8551Bezeq International Ltd.UnclassifiedIPv435
AS12491Gilat Telecom Ltd.UnclassifiedIPv424

Transit

Downstream networks

inferred

Networks for which AS13684 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 12

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

ASNetworkTypeFamiliesPaths seen
AS702Verizon BusinessUnclassifiedIPv4508
AS3356Level 3 Parent, LLCTransitIPv4 IPv6255
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4199
AS209CenturyLink Communications, LLCResidentialIPv4173
AS39686Eurofiber Nederland BVResidentialIPv4 IPv6163
AS703Verizon BusinessUnclassifiedIPv4151
AS2516KDDI CORPORATIONMobileIPv474
AS18229CtrlSHostingIPv459
AS8551Bezeq International Ltd.UnclassifiedIPv435
AS12491Gilat Telecom Ltd.UnclassifiedIPv424

Provenance

Where this comes from

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