asn.dev

Observed topology

AS211316 ADYEN2 Adyen N.V.

Unclassified RIPE

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

Transit

Upstream networks

All 26

Networks observed carrying traffic for AS211316: 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
AS8220COLT Technology Services Group LimitedHostingIPv4158
AS3356Level 3 Parent, LLCTransitIPv4154
AS216265ARISTO NETWORKS LTDUnclassifiedIPv490
AS2914NTT America, Inc.TransitIPv483
AS6461Zayo BandwidthTransitIPv482
AS9498BHARTI Airtel Ltd.MobileIPv458
AS5511Orange S.A.TransitIPv451
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv445
AS7473Singapore Telecommunications LtdUnclassifiedIPv433
AS20562Broadband Hosting B.V.HostingIPv432

Transit

Downstream networks

inferred

Networks for which AS211316 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 26

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

ASNetworkTypeFamiliesPaths seen
AS8220COLT Technology Services Group LimitedHostingIPv4160
AS3356Level 3 Parent, LLCTransitIPv4154
AS216265ARISTO NETWORKS LTDUnclassifiedIPv490
AS2914NTT America, Inc.TransitIPv483
AS6461Zayo BandwidthTransitIPv482
AS9498BHARTI Airtel Ltd.MobileIPv458
AS5511Orange S.A.TransitIPv451
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv445
AS7473Singapore Telecommunications LtdUnclassifiedIPv433
AS20562Broadband Hosting B.V.HostingIPv432

Provenance

Where this comes from

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