asn.dev

Observed topology

AS141039 PACKETHUBSA-AS-AP PacketHub S.A.

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS141039: 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,183
AS3257GTT Communications Inc.TransitIPv4 IPv6798
AS15440UAB "Baltnetos komunikacijos"UnclassifiedIPv4 IPv6117
AS6939Hurricane Electric LLCTransitIPv4 IPv688
AS13194UAB "Bite Lietuva"UnclassifiedIPv4 IPv688
AS1257Tele2 Sverige ABMobileIPv4 IPv65

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209854Cyberzone S.A.VPNIPv4 IPv6314
AS211192NetWave Inc.UnclassifiedIPv4295

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv61,454
AS3257GTT Communications Inc.TransitIPv4 IPv6885
AS209854Cyberzone S.A.VPNIPv4 IPv6314
AS211192NetWave Inc.UnclassifiedIPv4295
AS13194UAB "Bite Lietuva"UnclassifiedIPv4 IPv6264
AS15440UAB "Baltnetos komunikacijos"UnclassifiedIPv4 IPv6168
AS6939Hurricane Electric LLCTransitIPv4 IPv6107
AS1257Tele2 Sverige ABMobileIPv4 IPv610

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-25 12: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.