asn.dev

Observed topology

AS38254 ITLAB-AS-AP - Internet Technology Laboratory

Unclassified APNIC Educational/Research

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38254: 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
AS18423RAID Networks Co., Ltd.HostingIPv4 IPv6226
AS6939Hurricane Electric LLCTransitIPv4 IPv6136
AS7539National Center for High-performance ComputingEducationIPv42
AS24482SG.GSHostingIPv4 IPv62
AS38855Taiwan Digital Streaming Co.UnclassifiedIPv4 IPv62
AS18041Taiwan Digital Streaming Co.HostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS9267Pang-Wei TsaiUnclassifiedIPv6144
AS214821Wen-Ju, ChiangUnclassifiedIPv638
AS154392Singapore Institute of TechnologyUnclassifiedIPv626

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6382
AS18423RAID Networks Co., Ltd.HostingIPv4 IPv6260
AS9267Pang-Wei TsaiUnclassifiedIPv6144
AS214821Wen-Ju, ChiangUnclassifiedIPv6110
AS154392Singapore Institute of TechnologyUnclassifiedIPv626
AS7539National Center for High-performance ComputingEducationIPv42
AS24482SG.GSHostingIPv4 IPv62
AS38855Taiwan Digital Streaming Co.UnclassifiedIPv4 IPv62
AS18041Taiwan Digital Streaming Co.HostingIPv41

Provenance

Where this comes from

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