asn.dev

Observed topology

AS10098 HENDERSON-HK Towngas Telecommunications Fixed Network Ltd

Upstreams 9 carry this network
Downstreams 5 this network carries
Adjacent (IPv4) 16
Adjacent (IPv6) 6

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS10098: 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
AS140570Hong Kong Beecloud System Technology Services LimitedHostingIPv4 IPv61,501
AS6939Hurricane Electric LLCTransitIPv4332
AS3257GTT Communications Inc.TransitIPv4 IPv6152
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6147
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv4 IPv688
AS24482SG.GSHostingIPv4 IPv637
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv4 IPv630
AS9293NTT Com Asia LimitedUnclassifiedIPv424
AS8359MTS PJSCMobileIPv41

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.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS10132Towngas Telecommunications Fixed Network LimitedUnclassifiedIPv4976
AS134379TGGO COMPANY LIMITEDUnclassifiedIPv438
AS38478SunnyVision LimitedHostingIPv413
AS55858Speedy Group Corporation LimitedUnclassifiedIPv410
AS23881UDomain Web Hosting Company LtdHostingIPv42

Adjacency

Adjacent networks

22 shown

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

ASNetworkTypeFamiliesPaths seen
AS140570Hong Kong Beecloud System Technology Services LimitedHostingIPv4 IPv61,621
AS10132Towngas Telecommunications Fixed Network LimitedUnclassifiedIPv4976
AS6939Hurricane Electric LLCTransitIPv4865
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv4 IPv6192
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6160
AS3257GTT Communications Inc.TransitIPv4 IPv6154
AS24482SG.GSHostingIPv4 IPv694
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv4 IPv681
AS703Verizon BusinessUnclassifiedIPv468
AS8359MTS PJSCMobileIPv448
AS9002RETN LimitedUnclassifiedIPv447
AS134379TGGO COMPANY LIMITEDUnclassifiedIPv438
AS9293NTT Com Asia LimitedUnclassifiedIPv431
AS38478SunnyVision LimitedHostingIPv423
AS55858Speedy Group Corporation LimitedUnclassifiedIPv410
AS23881UDomain Web Hosting Company LtdHostingIPv42

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.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS10098, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 2 exchanges across 1 country and 1 region.

ExchangeLocationTheir addressMember ports
Hong Kong Internet ExchangeHong Kong, China123.255.91.116307
Equinix Internet Exchange Hong KongHong Kong, China2001:de8:7::1:98:1232

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Provenance

Where this comes from

Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.

Exchange presence comes from a separate dataset: the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.