asn.dev

Observed topology

AS30985 IKATELNET

Unclassified ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS30985: 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
AS8346IDDQD-ASResidentialIPv4 IPv64,244
AS29571Orange Côte d'IvoireResidentialIPv4 IPv62,021
AS5511Orange S.A.TransitIPv41,302

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS328284Société Malienne de Transmission et de DiffusionUnclassifiedIPv4295
AS328253ALPHA TELECOMMUNICATION MALI-ATEL-S.AResidentialIPv4 IPv6210
AS328126Orange TunisieHostingIPv4 IPv692

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8346IDDQD-ASResidentialIPv4 IPv64,277
AS29571Orange Côte d'IvoireResidentialIPv4 IPv62,054
AS5511Orange S.A.TransitIPv41,833
AS328284Société Malienne de Transmission et de DiffusionUnclassifiedIPv4295
AS328253ALPHA TELECOMMUNICATION MALI-ATEL-S.AResidentialIPv4 IPv6210
AS328126Orange TunisieHostingIPv4 IPv692

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.