Observed topology

AS206866 Gartel GARTEL, TELEFONIA Y COMUNICACION, S.L.

Unclassified RIPE Cable/DSL/ISP

Upstreams 3 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 2

Upstream graph Who carries AS206866, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS206866 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS206866: 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.

AS	Network	Type	Families	Paths seen
AS15704	XTRA TELECOM S.A.	Residential	IPv4	275
AS8903	LYNTIA NETWORKS S.A.	Unclassified	IPv4 IPv6	195
AS29119	AIRE NETWORKS DEL MEDITERRANEO SL UNIPERSONAL	Unclassified	IPv4 IPv6	106

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS211974	Airecom Internet, S.L.	Unclassified	IPv4	63
AS198968	Cyberneticos Hosting SL	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS15704	XTRA TELECOM S.A.	Residential	IPv4	304
AS8903	LYNTIA NETWORKS S.A.	Unclassified	IPv4 IPv6	208
AS29119	AIRE NETWORKS DEL MEDITERRANEO SL UNIPERSONAL	Unclassified	IPv4 IPv6	186
AS211974	Airecom Internet, S.L.	Unclassified	IPv4	63
AS198968	Cyberneticos Hosting SL	Unclassified	IPv4	59

Provenance

Where this comes from

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