asn.dev

Observed topology

AS200596 ADYEN Adyen N.V.

Unclassified ARIN

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

Transit

Upstream networks

All 37

Networks observed carrying traffic for AS200596: 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
AS3356Level 3 Parent, LLCTransitIPv4248
AS13335Cloudflare, Inc.HostingIPv4234
AS6461Zayo BandwidthTransitIPv4200
AS9498BHARTI Airtel Ltd.MobileIPv4157
AS2914NTT America, Inc.TransitIPv4131
AS4637Telstra GlobalUnclassifiedIPv4121
AS32787Akamai Technologies, Inc.HostingIPv4114
AS4826Vocus Connect International BackboneUnclassifiedIPv4108
AS8220COLT Technology Services Group LimitedHostingIPv469
AS1299Arelion Sweden ABTransitIPv453

All 37 upstreams →

Transit

Downstream networks

inferred

Networks for which AS200596 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 37

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4248
AS13335Cloudflare, Inc.HostingIPv4234
AS6461Zayo BandwidthTransitIPv4200
AS9498BHARTI Airtel Ltd.MobileIPv4157
AS2914NTT America, Inc.TransitIPv4131
AS4637Telstra GlobalUnclassifiedIPv4121
AS32787Akamai Technologies, Inc.HostingIPv4114
AS4826Vocus Connect International BackboneUnclassifiedIPv4108
AS8220COLT Technology Services Group LimitedHostingIPv469
AS1299Arelion Sweden ABTransitIPv453

All 37 adjacent →

Provenance

Where this comes from

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