asn.dev

Observed topology

AS208591 aitire Aitire S.L

Hosting RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS208591: 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 IPv6381
AS1299Arelion Sweden ABTransitIPv4 IPv669
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv637
AS174Cogent Communications, LLCTransitIPv430
AS24482SG.GSHostingIPv4 IPv614
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv611
AS5405Inter.link GmbHUnclassifiedIPv46
AS33891Core-Backbone GmbHHostingIPv46
AS25091IP-Max SAUnclassifiedIPv65
AS29632Netassist International EOODUnclassifiedIPv65

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS60667COMUNISTONE, S.L.UnclassifiedIPv4 IPv6169

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6611
AS60667COMUNISTONE, S.L.UnclassifiedIPv4 IPv6299
AS1299Arelion Sweden ABTransitIPv4 IPv697
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv655
AS174Cogent Communications, LLCTransitIPv439
AS24482SG.GSHostingIPv4 IPv620
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv617
AS33891Core-Backbone GmbHHostingIPv47
AS5405Inter.link GmbHUnclassifiedIPv46
AS29632Netassist International EOODUnclassifiedIPv66

Provenance

Where this comes from

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