Observed topology

AS12926 ARTELECOMPT Ar Telecom Autonomous System

Unclassified RIPE NSP

Upstreams 3 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 4

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12926: 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
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	327
AS29119	AIRE NETWORKS DEL MEDITERRANEO SL UNIPERSONAL	Unclassified	IPv4 IPv6	56
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	42

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS47784	Entidade de Servicos Partilhados da Administracao Publica, I.P.	Unclassified	IPv4 IPv6	322
AS211259	MBBLC NETWORKS LDA	Unclassified	IPv4	65
AS215306	R&D, LDA	Unclassified	IPv4	64

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	690
AS47784	Entidade de Servicos Partilhados da Administracao Publica, I.P.	Unclassified	IPv4 IPv6	322
AS29119	AIRE NETWORKS DEL MEDITERRANEO SL UNIPERSONAL	Unclassified	IPv4 IPv6	108
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	78
AS211259	MBBLC NETWORKS LDA	Unclassified	IPv4	65
AS215306	R&D, LDA	Unclassified	IPv4	64

Provenance

Where this comes from

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