asn.dev

Observed topology

AS8554 ATSAT ATSAT Autonomous System

Unclassified RIPE

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS8554: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6321
AS6939Hurricane Electric LLCTransitIPv4 IPv699
AS5511Orange S.A.TransitIPv460
AS33891Core-Backbone GmbHHostingIPv416
AS24482SG.GSHostingIPv4 IPv69
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv69
AS6696VERIXI SAUnclassifiedIPv48
AS12779IT.Gate S.p.A.UnclassifiedIPv48
AS20766Association "Gitoyen"UnclassifiedIPv48
AS34927iFog GmbHHostingIPv48

All 16 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS204818Hosteur SASUnclassifiedIPv459
AS200435Titan DataCenters France SASUnclassifiedIPv4 IPv67

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6321
AS5511Orange S.A.TransitIPv4 IPv6126
AS6939Hurricane Electric LLCTransitIPv4 IPv699
AS204818Hosteur SASUnclassifiedIPv459
AS33891Core-Backbone GmbHHostingIPv416
AS24482SG.GSHostingIPv4 IPv69
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv69
AS6696VERIXI SAUnclassifiedIPv48
AS12779IT.Gate S.p.A.UnclassifiedIPv48
AS20766Association "Gitoyen"UnclassifiedIPv48

All 18 adjacent →

Provenance

Where this comes from

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