Observed topology

AS18422 ITRINET-AS-TW - Industrial Technology Research Institute

Unclassified APNIC Educational/Research

Upstreams 7 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 4

Upstream graph Who carries AS18422, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS18422 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS17408	AboveNet Communications Taiwan	Unclassified	IPv4 IPv6	738
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	324
AS4780	Digital United Inc.	Residential	IPv4 IPv6	292
AS9924	Taiwan Fixed Network, Telco and Network Service Provider.	Residential	IPv4	123
AS24482	SG.GS	Hosting	IPv4 IPv6	15
AS7539	National Center for High-performance Computing	Education	IPv4	14
AS10133	Chief Telecom Inc.	Unclassified	IPv4	2

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS17408	AboveNet Communications Taiwan	Unclassified	IPv4 IPv6	738
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	324
AS4780	Digital United Inc.	Residential	IPv4 IPv6	292
AS9924	Taiwan Fixed Network, Telco and Network Service Provider.	Residential	IPv4	123
AS24482	SG.GS	Hosting	IPv4 IPv6	15
AS7539	National Center for High-performance Computing	Education	IPv4	14
AS10133	Chief Telecom Inc.	Unclassified	IPv4	2

Provenance

Where this comes from

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