asn.dev

Observed topology

AS210278 SKYIT-BB Sky Italia srl

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS210278: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6262
AS3356Level 3 Parent, LLCTransitIPv4 IPv6237
AS6939Hurricane Electric LLCTransitIPv4 IPv699
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv682
AS12779IT.Gate S.p.A.UnclassifiedIPv411
AS13030Init7 (Switzerland) Ltd.HostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207163Sky UK LimitedUnclassifiedIPv4118
AS60772Sky Italia srlHostingIPv473

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6328
AS1299Arelion Sweden ABTransitIPv4 IPv6314
AS6939Hurricane Electric LLCTransitIPv4 IPv6131
AS207163Sky UK LimitedUnclassifiedIPv4118
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv696
AS60772Sky Italia srlHostingIPv473
AS12779IT.Gate S.p.A.UnclassifiedIPv413
AS13030Init7 (Switzerland) Ltd.HostingIPv61

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.