asn.dev

Observed topology

AS35617 AIR2BITE-AS air2bite s.r.l.

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS35617: 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 IPv6401
AS5398Internet one SRLUnclassifiedIPv4 IPv6272
AS6939Hurricane Electric LLCTransitIPv4 IPv6145
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6126
AS8218Zayo Infrastructure France SAUnclassifiedIPv61
AS24482SG.GSHostingIPv61
AS29632Netassist International EOODUnclassifiedIPv61
AS31543myNet GmbHResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS29050Terrecablate Reti e Servizi S.R.L.UnclassifiedIPv4108
AS208578MACROTEL ITALIA SRLUnclassifiedIPv436
AS210105COMPUTING SERVICE S.R.L.UnclassifiedIPv420

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS41327Fiber Telecom S.p.A.ResidentialIPv4 IPv6600
AS5398Internet one SRLUnclassifiedIPv4 IPv6493
AS29050Terrecablate Reti e Servizi S.R.L.UnclassifiedIPv4472
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6234
AS6939Hurricane Electric LLCTransitIPv4 IPv6145
AS208578MACROTEL ITALIA SRLUnclassifiedIPv436
AS210105COMPUTING SERVICE S.R.L.UnclassifiedIPv420
AS8218Zayo Infrastructure France SAUnclassifiedIPv61
AS24482SG.GSHostingIPv61
AS29632Netassist International EOODUnclassifiedIPv61

Provenance

Where this comes from

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