asn.dev

Observed topology

AS34691 TLCWEB-AS Intendo S.r.l.

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34691: 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.UnclassifiedIPv493
AS41327Fiber Telecom S.p.A.ResidentialIPv483
AS28716Retelit Digital Services S.p.A.UnclassifiedIPv4 IPv659
AS6939Hurricane Electric LLCTransitIPv432
AS24482SG.GSHostingIPv43
AS59919Brainbox S.r.l.ResidentialIPv43
AS8218Zayo Infrastructure France SAUnclassifiedIPv41
AS31543myNet GmbHResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS47735NOWIRE s.r.l.UnclassifiedIPv4183
AS198349Baleno S.r.l.UnclassifiedIPv4112
AS58316WiGate S.r.l.UnclassifiedIPv4104
AS218793Royal Web s.r.l.s.UnclassifiedIPv460
AS205891WeNetwork SRLResidentialIPv452

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS41327Fiber Telecom S.p.A.ResidentialIPv4367
AS12779IT.Gate S.p.A.UnclassifiedIPv4234
AS47735NOWIRE s.r.l.UnclassifiedIPv4183
AS198349Baleno S.r.l.UnclassifiedIPv4112
AS58316WiGate S.r.l.UnclassifiedIPv4104
AS28716Retelit Digital Services S.p.A.UnclassifiedIPv4 IPv697
AS6939Hurricane Electric LLCTransitIPv471
AS218793Royal Web s.r.l.s.UnclassifiedIPv460
AS205891WeNetwork SRLResidentialIPv452
AS24482SG.GSHostingIPv410

All 13 adjacent →

Provenance

Where this comes from

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