asn.dev

Observed topology

AS45642 JASTEL-NETWORK-TH-NIX-AP Jasmine International Tower

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS45642: 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.GSHostingIPv43

Transit

Downstream networks

All 25

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

ASNetworkTypeFamiliesPaths seen
AS55423JasTel NetworkUnclassifiedIPv4 IPv6100
AS136907HUAWEI CLOUDSHostingIPv4 IPv652
AS56309Siamdata Communication Co.,Ltd.UnclassifiedIPv446
AS7616JasTel NetworkUnclassifiedIPv4 IPv632
AS142299CLOUDFOREST CO., LTD.HostingIPv426
AS147176NZ Network Enterprise Co., Ltd.HostingIPv420
AS45455Two S One N Co Ltd, Internet Service Provider and IT SolutionsUnclassifiedIPv411
AS138156CSNE Co., Ltd.UnclassifiedIPv410
AS135290SAN-IDCUnclassifiedIPv45
AS135589Internet Maekhong Network Company LimitedHostingIPv45

Adjacency

Adjacent networks

All 27

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

ASNetworkTypeFamiliesPaths seen
AS55423JasTel NetworkUnclassifiedIPv4 IPv6545
AS24482SG.GSHostingIPv4 IPv6381
AS136907HUAWEI CLOUDSHostingIPv4 IPv652
AS56309Siamdata Communication Co.,Ltd.UnclassifiedIPv446
AS7616JasTel NetworkUnclassifiedIPv4 IPv634
AS142299CLOUDFOREST CO., LTD.HostingIPv430
AS147176NZ Network Enterprise Co., Ltd.HostingIPv421
AS45455Two S One N Co Ltd, Internet Service Provider and IT SolutionsUnclassifiedIPv411
AS138156CSNE Co., Ltd.UnclassifiedIPv410
AS135290SAN-IDCUnclassifiedIPv48

Provenance

Where this comes from

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