asn.dev

Observed topology

AS8968 BT-Italia RETELIT-X S.R.L.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS8968: 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
AS3302Retelit Digital Services S.p.A.UnclassifiedIPv4 IPv61,604
AS5400British Telecommunications LimitedUnclassifiedIPv4 IPv6210

Transit

Downstream networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS3313RETELIT-X S.R.L.UnclassifiedIPv4 IPv6755
AS33942IREN ENERGIA S.P.AUnclassifiedIPv4456
AS12797RETELIT-X S.R.L.UnclassifiedIPv4341
AS39729REGISTER S.P.A.HostingIPv4239
AS12363REGISTER S.P.A.HostingIPv4 IPv6201
AS35130REGISTER S.P.A.HostingIPv4186
AS43602Esprinet S.P.A.UnclassifiedIPv4165
AS25518Zucchetti SpaUnclassifiedIPv4122
AS35051Nexi Payments S.P.A.UnclassifiedIPv4110
AS34599EI TOWERS S.P.A.UnclassifiedIPv477

All 13 downstreams →

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS3302Retelit Digital Services S.p.A.UnclassifiedIPv4 IPv62,826
AS5400British Telecommunications LimitedUnclassifiedIPv4 IPv61,814
AS3313RETELIT-X S.R.L.UnclassifiedIPv4 IPv6799
AS33942IREN ENERGIA S.P.AUnclassifiedIPv4456
AS12797RETELIT-X S.R.L.UnclassifiedIPv4341
AS39729REGISTER S.P.A.HostingIPv4239
AS12363REGISTER S.P.A.HostingIPv4 IPv6201
AS35130REGISTER S.P.A.HostingIPv4186
AS43602Esprinet S.P.A.UnclassifiedIPv4165
AS25518Zucchetti SpaUnclassifiedIPv4122

All 15 adjacent →

Provenance

Where this comes from

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