asn.dev

Observed topology

AS43515 YOUTUBE YOUTUBE

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS43515: 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, LLCTransitIPv4 IPv61,602
AS1299Arelion Sweden ABTransitIPv4 IPv61,310
AS174Cogent Communications, LLCTransitIPv4 IPv6879
AS3257GTT Communications Inc.TransitIPv4 IPv6770
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6493
AS15169Google LLCHostingIPv4 IPv6296
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv678
AS1273IDDQD-ASBusinessIPv4 IPv635

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS19527Google LLCUnclassifiedIPv438

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,606
AS1299Arelion Sweden ABTransitIPv4 IPv61,310
AS174Cogent Communications, LLCTransitIPv4 IPv6892
AS3257GTT Communications Inc.TransitIPv4 IPv6785
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6499
AS15169Google LLCHostingIPv4 IPv6296
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv678
AS19527Google LLCUnclassifiedIPv438
AS1273IDDQD-ASBusinessIPv4 IPv635

Provenance

Where this comes from

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