asn.dev

Observed topology

AS10226 ETL-IX-AS-AP ETL Company Limited

Mobile APNIC Cable/DSL/ISP

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS10226: 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
AS23764CTGNetUnclassifiedIPv4 IPv62,082
AS1299Arelion Sweden ABTransitIPv4516
AS6939Hurricane Electric LLCTransitIPv4 IPv6470
AS3491PCCW Global (HK) Ltd.TransitIPv4107
AS38001NewMedia Express Pte LtdHostingIPv4 IPv661
AS24482SG.GSHostingIPv4 IPv660
AS17639Converge ICT Solutions Inc.UnclassifiedIPv44
AS33891Core-Backbone GmbHHostingIPv44
AS132132MyRepublic Ltd.ResidentialIPv44
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv42

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS153966Joint Development BankUnclassifiedIPv416
AS140631Global Digital Management Solutions Co LtdUnclassifiedIPv44

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS23764CTGNetUnclassifiedIPv4 IPv62,098
AS1299Arelion Sweden ABTransitIPv4520
AS6939Hurricane Electric LLCTransitIPv4 IPv6470
AS3491PCCW Global (HK) Ltd.TransitIPv4107
AS38001NewMedia Express Pte LtdHostingIPv4 IPv661
AS24482SG.GSHostingIPv4 IPv660
AS153966Joint Development BankUnclassifiedIPv416
AS17639Converge ICT Solutions Inc.UnclassifiedIPv44
AS33891Core-Backbone GmbHHostingIPv44
AS132132MyRepublic Ltd.ResidentialIPv44

All 13 adjacent →

Provenance

Where this comes from

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