asn.dev

Observed topology

AS38047 TAIWAN-TELECOM - Taiwan Telecom

Hosting ARIN Network Services

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38047: 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
AS20473The Constant Company, LLCHostingIPv4 IPv6570
AS134823Sky Digital Co., Ltd.ResidentialIPv4 IPv6431
AS17408AboveNet Communications TaiwanUnclassifiedIPv4 IPv6291
AS6939Hurricane Electric LLCTransitIPv4 IPv6170
AS24482SG.GSHostingIPv4 IPv612
AS38855Taiwan Digital Streaming Co.UnclassifiedIPv4 IPv612

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS134176Cloudie LimitedUnclassifiedIPv4814

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS134176Cloudie LimitedUnclassifiedIPv4873
AS20473The Constant Company, LLCHostingIPv4 IPv6570
AS3491PCCW Global (HK) Ltd.TransitIPv4549
AS134823Sky Digital Co., Ltd.ResidentialIPv4 IPv6431
AS17408AboveNet Communications TaiwanUnclassifiedIPv4 IPv6291
AS1299Arelion Sweden ABTransitIPv4196
AS6939Hurricane Electric LLCTransitIPv4 IPv6170
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv470
AS24482SG.GSHostingIPv4 IPv626
AS55720Gigabit Hosting Sdn BhdHostingIPv416

All 13 adjacent →

Provenance

Where this comes from

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