asn.dev

Observed topology

AS207697 IMMOBILIARE_

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS207697: 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
AS12874Fastweb SpAResidentialIPv4193
AS203201INFRASTRUCTURE ITALIA COLO S.R.L.ResidentialIPv482
AS3269Telecom Italia S.p.A.ResidentialIPv45
AS24482SG.GSHostingIPv45
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv45
AS31543myNet GmbHResidentialIPv45
AS59919Brainbox S.r.l.ResidentialIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207694PKP Linia Hutnicza Szerokotorowa Sp. z o.o.UnclassifiedIPv458

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12874Fastweb SpAResidentialIPv4193
AS207694PKP Linia Hutnicza Szerokotorowa Sp. z o.o.UnclassifiedIPv4116
AS203201INFRASTRUCTURE ITALIA COLO S.R.L.ResidentialIPv482
AS3269Telecom Italia S.p.A.ResidentialIPv45
AS24482SG.GSHostingIPv45
AS29075IELO-LIAZO SERVICES SASUnclassifiedIPv45
AS31543myNet GmbHResidentialIPv45
AS59919Brainbox S.r.l.ResidentialIPv45

Provenance

Where this comes from

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