asn.dev

Observed topology

AS13280 H3GIE Three Ireland (Hutchison) limited

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS13280: 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
AS6461Zayo BandwidthTransitIPv41,782
AS3257GTT Communications Inc.TransitIPv41,024
AS6939Hurricane Electric LLCTransitIPv4480
AS9002RETN LimitedUnclassifiedIPv4438
AS1299Arelion Sweden ABTransitIPv4354
AS20562Broadband Hosting B.V.HostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49406Fast Wireless Internet LtdUnclassifiedIPv459
AS23154Sanmina-SCI CorporationUnclassifiedIPv413
AS206051ARAMARK N.VUnclassifiedIPv411

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv41,846
AS3257GTT Communications Inc.TransitIPv41,026
AS6939Hurricane Electric LLCTransitIPv4489
AS9002RETN LimitedUnclassifiedIPv4446
AS1299Arelion Sweden ABTransitIPv4354
AS49406Fast Wireless Internet LtdUnclassifiedIPv459
AS23154Sanmina-SCI CorporationUnclassifiedIPv413
AS206051ARAMARK N.VUnclassifiedIPv411
AS20562Broadband Hosting B.V.HostingIPv41

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.