asn.dev

Observed topology

AS4741 SAMART-INFONET-AS - Samart Infonet Co., Ltd.

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS4741: 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
AS45629JasTel Network International GatewayResidentialIPv42,161
AS38082True International Gateway Co., Ltd.UnclassifiedIPv4 IPv6263
AS45796UIH / BB ConnectUnclassifiedIPv4 IPv657
AS24482SG.GSHostingIPv4 IPv637
AS45642Jasmine International TowerUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS17901One to One Contacts Public Company Limited.UnclassifiedIPv4224
AS9715SAMART Corp (Excise-Direct Coding Data Center)UnclassifiedIPv4108
AS23925Siam Sport Syndicate Public Co.,Ltd.UnclassifiedIPv466

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS45629JasTel Network International GatewayResidentialIPv42,493
AS38082True International Gateway Co., Ltd.UnclassifiedIPv4 IPv6324
AS17901One to One Contacts Public Company Limited.UnclassifiedIPv4224
AS9715SAMART Corp (Excise-Direct Coding Data Center)UnclassifiedIPv4108
AS23925Siam Sport Syndicate Public Co.,Ltd.UnclassifiedIPv466
AS45796UIH / BB ConnectUnclassifiedIPv4 IPv657
AS24482SG.GSHostingIPv4 IPv642
AS45642Jasmine International TowerUnclassifiedIPv42

Provenance

Where this comes from

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