asn.dev

Observed topology

AS28929 ASDASD-AS ASDASD srl a socio unico

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS28929: 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
AS174Cogent Communications, LLCTransitIPv4 IPv6215
AS3257GTT Communications Inc.TransitIPv4104
AS6939Hurricane Electric LLCTransitIPv467
AS3303Swisscom (Schweiz) AGResidentialIPv47
AS12779IT.Gate S.p.A.UnclassifiedIPv47
AS4657StarHub LtdResidentialIPv45
AS12552GlobalConnect ABUnclassifiedIPv45
AS24482SG.GSHostingIPv45
AS33891Core-Backbone GmbHHostingIPv45
AS37100SEACOM LimitedUnclassifiedIPv45

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6215
AS3257GTT Communications Inc.TransitIPv4104
AS6939Hurricane Electric LLCTransitIPv467
AS3303Swisscom (Schweiz) AGResidentialIPv47
AS12779IT.Gate S.p.A.UnclassifiedIPv47
AS4657StarHub LtdResidentialIPv45
AS12552GlobalConnect ABUnclassifiedIPv45
AS24482SG.GSHostingIPv45
AS33891Core-Backbone GmbHHostingIPv45
AS37100SEACOM LimitedUnclassifiedIPv45

Provenance

Where this comes from

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