asn.dev

Observed topology

AS8739 ICDSOFT

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS8739: 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
AS3356Level 3 Parent, LLCTransitIPv4656
AS174Cogent Communications, LLCTransitIPv4374
AS34224Neterra Ltd.UnclassifiedIPv4350
AS9304HGC Global Communications LimitedHostingIPv4147
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv456
AS24482SG.GSHostingIPv46
AS41313"NOVATEL" EOODUnclassifiedIPv46
AS8359MTS PJSCMobileIPv44
AS9930TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, MalaysiaUnclassifiedIPv44

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4656
AS174Cogent Communications, LLCTransitIPv4374
AS34224Neterra Ltd.UnclassifiedIPv4350
AS9304HGC Global Communications LimitedHostingIPv4147
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv456
AS24482SG.GSHostingIPv46
AS41313"NOVATEL" EOODUnclassifiedIPv46
AS8359MTS PJSCMobileIPv44
AS9930TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, MalaysiaUnclassifiedIPv44

Provenance

Where this comes from

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