asn.dev

Observed topology

AS6515 DACSNX-ISP - DACS-IX

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS6515: 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 LLCTransitIPv4 IPv6379
AS6461Zayo BandwidthTransitIPv4 IPv6101
AS174Cogent Communications, LLCTransitIPv4 IPv693
AS24482SG.GSHostingIPv4 IPv66
AS13030Init7 (Switzerland) Ltd.HostingIPv64
AS3303Swisscom (Schweiz) AGResidentialIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS19528Meridian Parkway Data Center Owner, LLCHostingIPv4449
AS7010DACS-IXUnclassifiedIPv4 IPv6387
AS7124DACS-IXUnclassifiedIPv4 IPv6343
AS30622Venable LLPUnclassifiedIPv4166
AS203939Mosaic Data Services, Inc.HostingIPv4 IPv6123
AS16557Colo SolutionsHostingIPv463

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,618
AS19528Meridian Parkway Data Center Owner, LLCHostingIPv4536
AS7010DACS-IXUnclassifiedIPv4 IPv6405
AS7124DACS-IXUnclassifiedIPv4 IPv6343
AS6461Zayo BandwidthTransitIPv4 IPv6312
AS174Cogent Communications, LLCTransitIPv4 IPv6220
AS30622Venable LLPUnclassifiedIPv4166
AS203939Mosaic Data Services, Inc.HostingIPv4 IPv6123
AS16557Colo SolutionsHostingIPv463
AS24482SG.GSHostingIPv4 IPv632

All 13 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.