asn.dev

Observed topology

AS18206 TTSSB-MY TM TECHNOLOGY SERVICES SDN. BHD.

Hosting APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS18206: 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
AS4788TM TECHNOLOGY SERVICES SDN. BHD.MobileIPv4 IPv63,172
AS58453China Mobile International LimitedUnclassifiedIPv4 IPv6651
AS19551Incapsula IncHostingIPv4177
AS8757NSFOCUS, Inc.UnclassifiedIPv4160
AS24482SG.GSHostingIPv4 IPv6108
AS55720Gigabit Hosting Sdn BhdHostingIPv4103

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS17971TM TECHNOLOGY SERVICES SDN. BHD.HostingIPv42,943
AS150455SNS NETWORK (M) SDN BHDUnclassifiedIPv462

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4788TM TECHNOLOGY SERVICES SDN. BHD.MobileIPv4 IPv63,601
AS58453China Mobile International LimitedUnclassifiedIPv4 IPv63,225
AS17971TM TECHNOLOGY SERVICES SDN. BHD.HostingIPv42,947
AS19551Incapsula IncHostingIPv4177
AS8757NSFOCUS, Inc.UnclassifiedIPv4160
AS24482SG.GSHostingIPv4 IPv6111
AS55720Gigabit Hosting Sdn BhdHostingIPv4106
AS150455SNS NETWORK (M) SDN BHDUnclassifiedIPv462

Provenance

Where this comes from

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