asn.dev

Observed topology

AS45910 ISYSTEMTECH-HK i-System Technology Limited

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS45910: 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
AS6939Hurricane Electric LLCTransitIPv6690
AS140570Hong Kong Beecloud System Technology Services LimitedHostingIPv4 IPv6508
AS9381HKBN Enterprise Solutions HK LimitedHostingIPv4458
AS24482SG.GSHostingIPv4 IPv638
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv432
AS9930TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, MalaysiaUnclassifiedIPv416

Transit

Downstream networks

inferred

Networks for which AS45910 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 AS45910 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv6690
AS140570Hong Kong Beecloud System Technology Services LimitedHostingIPv4 IPv6508
AS9381HKBN Enterprise Solutions HK LimitedHostingIPv4458
AS24482SG.GSHostingIPv4 IPv638
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv432
AS9930TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, MalaysiaUnclassifiedIPv416

Provenance

Where this comes from

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