asn.dev

Observed topology

AS45938 NUCLEUS-CONNECT-SG 3 Tai Seng drive # 04-00

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS45938: 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
AS4657StarHub LtdResidentialIPv4 IPv6630

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS135008GOVERNMENT TECHNOLOGY AGENCYUnclassifiedIPv4 IPv6943
AS133387GOVERNMENT TECHNOLOGY AGENCYUnclassifiedIPv4 IPv6243
AS132286GOVERNMENT TECHNOLOGY AGENCYUnclassifiedIPv4180
AS140592GOVERNMENT TECHNOLOGY AGENCYUnclassifiedIPv4178
AS136601GOVERNMENT TECHNOLOGY AGENCYUnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS140928T20025UnclassifiedIPv4 IPv61,603
AS135008GOVERNMENT TECHNOLOGY AGENCYUnclassifiedIPv4 IPv6943
AS4657StarHub LtdResidentialIPv4 IPv6630
AS133387GOVERNMENT TECHNOLOGY AGENCYUnclassifiedIPv4 IPv6243
AS132286GOVERNMENT TECHNOLOGY AGENCYUnclassifiedIPv4180
AS140592GOVERNMENT TECHNOLOGY AGENCYUnclassifiedIPv4178
AS136601GOVERNMENT TECHNOLOGY AGENCYUnclassifiedIPv459

Provenance

Where this comes from

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