asn.dev

Observed topology

AS58436 SECUREAX-SG-AS-AP SECUREAX PTE LTD

Unclassified APNIC Enterprise

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58436: 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
AS24482SG.GSHostingIPv4 IPv6221
AS6939Hurricane Electric LLCTransitIPv4 IPv619
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv65
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv65
AS38001NewMedia Express Pte LtdHostingIPv43
AS61292Blix Group ASUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS201612nic.at GmbHUnclassifiedIPv4 IPv618

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS24482SG.GSHostingIPv4 IPv6238
AS6939Hurricane Electric LLCTransitIPv4 IPv622
AS201612nic.at GmbHUnclassifiedIPv4 IPv618
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv67
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv65
AS38001NewMedia Express Pte LtdHostingIPv44
AS61292Blix Group ASUnclassifiedIPv63

Provenance

Where this comes from

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