asn.dev

Observed topology

AS200760 ELOGIC-AS Elogic Srl - Cloud Services

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS200760: 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
AS3356Level 3 Parent, LLCTransitIPv4349
AS28716Retelit Digital Services S.p.A.UnclassifiedIPv4177
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6144
AS6939Hurricane Electric LLCTransitIPv4 IPv696
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv611
AS24482SG.GSHostingIPv4 IPv611
AS31543myNet GmbHResidentialIPv4 IPv611
AS59919Brainbox S.r.l.ResidentialIPv410
AS29632Netassist International EOODUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208761Maggioli S.p.a.UnclassifiedIPv4233

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4473
AS28716Retelit Digital Services S.p.A.UnclassifiedIPv4233
AS208761Maggioli S.p.a.UnclassifiedIPv4233
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv6166
AS6939Hurricane Electric LLCTransitIPv4 IPv6120
AS24482SG.GSHostingIPv4 IPv614
AS59919Brainbox S.r.l.ResidentialIPv413
AS31543myNet GmbHResidentialIPv4 IPv612
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv611
AS29632Netassist International EOODUnclassifiedIPv61

Provenance

Where this comes from

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