asn.dev

Observed topology

AS6895 ESPANIX-RS-AS Neutral Interconect Exchange for Spain

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS6895: 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 IPv637
AS33891Core-Backbone GmbHHostingIPv44
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv63
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv63
AS8218Zayo Infrastructure France SAUnclassifiedIPv42
AS23764CTGNetUnclassifiedIPv42
AS29632Netassist International EOODUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208591Aitire S.LHostingIPv43
AS201746Olivenet Network S.L.ResidentialIPv42
AS29119AIRE NETWORKS DEL MEDITERRANEO SL UNIPERSONALUnclassifiedIPv41
AS208569Norvoz Telecom, S.L.UnclassifiedIPv41

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv637
AS23764CTGNetUnclassifiedIPv49
AS33891Core-Backbone GmbHHostingIPv44
AS3303Swisscom (Schweiz) AGResidentialIPv4 IPv63
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv63
AS208591Aitire S.LHostingIPv43
AS8218Zayo Infrastructure France SAUnclassifiedIPv42
AS29632Netassist International EOODUnclassifiedIPv62
AS201746Olivenet Network S.L.ResidentialIPv42
AS29119AIRE NETWORKS DEL MEDITERRANEO SL UNIPERSONALUnclassifiedIPv41

Provenance

Where this comes from

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