asn.dev

Observed topology

AS5438 ATI-

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS5438: 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
AS2609IDDQD-ASUnclassifiedIPv41,862

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS37705TOPNETUnclassifiedIPv4 IPv66,259
AS31245Agence Tunisienne Internet - ATI - Agence Tunisienne InternetUnclassifiedIPv4 IPv63,271
AS328880STE INTERNET SMART SOLUTIONSUnclassifiedIPv42,403
AS2609IDDQD-ASUnclassifiedIPv460
AS327969Arab Tunisian BankUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2609IDDQD-ASUnclassifiedIPv4 IPv614,279
AS37705TOPNETUnclassifiedIPv4 IPv66,379
AS31245Agence Tunisienne Internet - ATI - Agence Tunisienne InternetUnclassifiedIPv4 IPv63,271
AS328880STE INTERNET SMART SOLUTIONSUnclassifiedIPv42,523
AS329563STE CHIFCOUnclassifiedIPv4119
AS37693OOREDOO TUNISIE SAMobileIPv465
AS327969Arab Tunisian BankUnclassifiedIPv460

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-28 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.