asn.dev

Observed topology

AS39356 AVANTI-UK-AS

Residential RIPE

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

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS39356: 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
AS13335Cloudflare, Inc.HostingIPv4161
AS3356Level 3 Parent, LLCTransitIPv4 IPv6136
AS6939Hurricane Electric LLCTransitIPv4 IPv670
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv618
AS3320Deutsche Telekom AGMobileIPv4 IPv615
AS24482SG.GSHostingIPv4 IPv67
AS48185team.blue NVUnclassifiedIPv4 IPv67
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv67
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv67
AS9002RETN LimitedUnclassifiedIPv66

All 22 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS328306Avanti Communications South Africa (Pty) LtdUnclassifiedIPv460

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6184
AS13335Cloudflare, Inc.HostingIPv4161
AS6939Hurricane Electric LLCTransitIPv4 IPv670
AS328306Avanti Communications South Africa (Pty) LtdUnclassifiedIPv460
AS3320Deutsche Telekom AGMobileIPv4 IPv627
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv618
AS24482SG.GSHostingIPv4 IPv67
AS48185team.blue NVUnclassifiedIPv4 IPv67
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv67
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv67

All 23 adjacent →

Provenance

Where this comes from

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