asn.dev

Observed topology

AS200043 CESENA-NET-SRL

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS200043: 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
AS9002RETN LimitedUnclassifiedIPv4391
AS12779IT.Gate S.p.A.UnclassifiedIPv4351
AS6939Hurricane Electric LLCTransitIPv4112
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv460
AS24482SG.GSHostingIPv416
AS59919Brainbox S.r.l.ResidentialIPv416
AS31543myNet GmbHResidentialIPv414

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS62290Tecnoservizi S.r.l.UnclassifiedIPv4240
AS50541ZINCA S.R.L.UnclassifiedIPv4180

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS9002RETN LimitedUnclassifiedIPv4615
AS12779IT.Gate S.p.A.UnclassifiedIPv4529
AS62290Tecnoservizi S.r.l.UnclassifiedIPv4300
AS50541ZINCA S.R.L.UnclassifiedIPv4180
AS6939Hurricane Electric LLCTransitIPv4168
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv460
AS59919Brainbox S.r.l.ResidentialIPv424
AS24482SG.GSHostingIPv423
AS31543myNet GmbHResidentialIPv421

Provenance

Where this comes from

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