asn.dev

Observed topology

AS34606 ASN-BBBELL B.B.Bell SPA

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34606: 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
AS12779IT.Gate S.p.A.UnclassifiedIPv4 IPv6446
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4222
AS6939Hurricane Electric LLCTransitIPv4 IPv6104
AS24482SG.GSHostingIPv4 IPv614
AS34019Hivane AssociationUnclassifiedIPv4 IPv614
AS3303Swisscom (Schweiz) AGResidentialIPv413
AS59919Brainbox S.r.l.ResidentialIPv413

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS47568LAN SERVICE s.r.l.UnclassifiedIPv457
AS202094FINDER SpAUnclassifiedIPv441

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS12779IT.Gate S.p.A.UnclassifiedIPv4 IPv6524
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4222
AS6939Hurricane Electric LLCTransitIPv4 IPv6111
AS47568LAN SERVICE s.r.l.UnclassifiedIPv457
AS202094FINDER SpAUnclassifiedIPv441
AS24482SG.GSHostingIPv4 IPv615
AS34019Hivane AssociationUnclassifiedIPv4 IPv615
AS3303Swisscom (Schweiz) AGResidentialIPv414
AS59919Brainbox S.r.l.ResidentialIPv414
AS37721Virtual Technologies & SolutionsResidentialIPv44

All 12 adjacent →

Provenance

Where this comes from

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