asn.dev

Observed topology

AS29582 SATCOM-AS

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS29582: 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
AS57344Telehouse EADResidentialIPv4 IPv66,740
AS6939Hurricane Electric LLCTransitIPv41,167
AS44901Belcloud LTDHostingIPv4171
AS41313"NOVATEL" EOODUnclassifiedIPv4 IPv6167
AS8218Zayo Infrastructure France SAUnclassifiedIPv4123

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS1978975KOM OODUnclassifiedIPv43,652
AS58079Skynet LtdUnclassifiedIPv4949
AS198127Hristo BogdanovUnclassifiedIPv4 IPv680
AS203312Global Pharma Centre JSCUnclassifiedIPv422

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS57344Telehouse EADResidentialIPv4 IPv69,777
AS1978975KOM OODUnclassifiedIPv43,652
AS6939Hurricane Electric LLCTransitIPv41,983
AS58079Skynet LtdUnclassifiedIPv4949
AS41313"NOVATEL" EOODUnclassifiedIPv4 IPv6929
AS8218Zayo Infrastructure France SAUnclassifiedIPv4207
AS44901Belcloud LTDHostingIPv4171
AS198127Hristo BogdanovUnclassifiedIPv4 IPv680
AS203312Global Pharma Centre JSCUnclassifiedIPv422
AS8717A1 Bulgaria EADResidentialIPv43

All 11 adjacent →

Provenance

Where this comes from

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