asn.dev

Observed topology

AS35612 NGI-AS EOLO S.p.A.

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS35612: 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
AS174Cogent Communications, LLCTransitIPv4 IPv6491
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6320
AS6461Zayo BandwidthTransitIPv4 IPv6319
AS6939Hurricane Electric LLCTransitIPv4 IPv6163
AS24482SG.GSHostingIPv4 IPv616
AS3303Swisscom (Schweiz) AGResidentialIPv415
AS31543myNet GmbHResidentialIPv415
AS34019Hivane AssociationUnclassifiedIPv415
AS59919Brainbox S.r.l.ResidentialIPv415
AS13030Init7 (Switzerland) Ltd.HostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS39217ELMEC INFORMATICA S.P.A.UnclassifiedIPv4 IPv6248
AS201946S.P.A.UnclassifiedIPv474
AS214164INTERPORTO PADOVA HALL S.P.A.UnclassifiedIPv411

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6574
AS6461Zayo BandwidthTransitIPv4 IPv6474
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6366
AS39217ELMEC INFORMATICA S.P.A.UnclassifiedIPv4 IPv6248
AS6939Hurricane Electric LLCTransitIPv4 IPv6198
AS201946S.P.A.UnclassifiedIPv474
AS3303Swisscom (Schweiz) AGResidentialIPv422
AS24482SG.GSHostingIPv4 IPv619
AS31543myNet GmbHResidentialIPv416
AS34019Hivane AssociationUnclassifiedIPv416

All 14 adjacent →

Provenance

Where this comes from

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