asn.dev

Observed topology

AS34758 AXERA-ASN34758 Axera S.P.A.

Residential RIPE

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

Transit

Upstream networks

All 18

Networks observed carrying traffic for AS34758: 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 IPv6783
AS9002RETN LimitedUnclassifiedIPv4 IPv6347
AS6939Hurricane Electric LLCTransitIPv4 IPv6226
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6151
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv660
AS24482SG.GSHostingIPv4 IPv631
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv631
AS3303Swisscom (Schweiz) AGResidentialIPv429
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv429
AS4657StarHub LtdResidentialIPv429

All 18 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS13097Axera SpAUnclassifiedIPv4183
AS205729MAGIS S.P.A.UnclassifiedIPv460

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS41327Fiber Telecom S.p.A.ResidentialIPv4 IPv6887
AS9002RETN LimitedUnclassifiedIPv4 IPv6402
AS6939Hurricane Electric LLCTransitIPv4 IPv6254
AS13097Axera SpAUnclassifiedIPv4183
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6171
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv668
AS205729MAGIS S.P.A.UnclassifiedIPv460
AS24482SG.GSHostingIPv4 IPv635
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv635
AS3303Swisscom (Schweiz) AGResidentialIPv433

All 20 adjacent →

Provenance

Where this comes from

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