asn.dev

Observed topology

AS203059 VION-AS Consorzio Energetico Val Venosta Soc. Coop.

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS203059: 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
AS41327Fiber Telecom S.p.A.ResidentialIPv4 IPv61,546
AS34347HALLAG Kommunal GmbHResidentialIPv4 IPv6973
AS6939Hurricane Electric LLCTransitIPv4 IPv6346
AS24482SG.GSHostingIPv4 IPv649
AS59919Brainbox S.r.l.ResidentialIPv448
AS205099DOLOMITES NETWORK S.R.L.ResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205099DOLOMITES NETWORK S.R.L.ResidentialIPv4 IPv66

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS41327Fiber Telecom S.p.A.ResidentialIPv4 IPv61,546
AS34347HALLAG Kommunal GmbHResidentialIPv4 IPv6979
AS6939Hurricane Electric LLCTransitIPv4 IPv6346
AS24482SG.GSHostingIPv4 IPv649
AS59919Brainbox S.r.l.ResidentialIPv448
AS205099DOLOMITES NETWORK S.R.L.ResidentialIPv4 IPv68

Provenance

Where this comes from

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