asn.dev

Observed topology

AS31059 SIA "AVELACOM"

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS31059: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208783SIA "AVELACOM"UnclassifiedIPv4294

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS208783SIA "AVELACOM"UnclassifiedIPv4294
AS41095IPTP LTDHostingIPv495
AS174Cogent Communications, LLCTransitIPv466
AS3223Voxility LLPHostingIPv448
AS3257GTT Communications Inc.TransitIPv431
AS4657StarHub LtdResidentialIPv425
AS1299Arelion Sweden ABTransitIPv423
AS6939Hurricane Electric LLCTransitIPv49
AS215182Avelacom Business Ltd.UnclassifiedIPv48
AS1836green.ch AGResidentialIPv43

Provenance

Where this comes from

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