asn.dev

Observed topology

AS147049 PACKETHUBSA-AS-AP PacketHub S.A.

Unclassified APNIC

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

Transit

Upstream networks

All 24

Networks observed carrying traffic for AS147049: 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
AS1299Arelion Sweden ABTransitIPv4 IPv61,361
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6932
AS6461Zayo BandwidthTransitIPv4 IPv6721
AS3257GTT Communications Inc.TransitIPv4 IPv6615
AS2914NTT America, Inc.TransitIPv4 IPv6455
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6327
AS6939Hurricane Electric LLCTransitIPv4 IPv6320
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6277
AS4637Telstra GlobalUnclassifiedIPv4 IPv6265
AS24482SG.GSHostingIPv4 IPv6137

All 24 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209854Cyberzone S.A.VPNIPv4 IPv61,608
AS211192NetWave Inc.UnclassifiedIPv4557

Adjacency

Adjacent networks

All 26

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv61,717
AS209854Cyberzone S.A.VPNIPv4 IPv61,608
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv61,274
AS6461Zayo BandwidthTransitIPv4 IPv6875
AS2914NTT America, Inc.TransitIPv4 IPv6805
AS3257GTT Communications Inc.TransitIPv4 IPv6675
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6557
AS211192NetWave Inc.UnclassifiedIPv4557
AS6939Hurricane Electric LLCTransitIPv4 IPv6529
AS24482SG.GSHostingIPv4 IPv6314

All 26 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.