asn.dev

Observed topology

AS6717 AS6717 UK ISP

Residential RIPE

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS6717: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6168
AS3257GTT Communications Inc.TransitIPv4 IPv678
AS6939Hurricane Electric LLCTransitIPv424
AS34549meerfarbig GmbH & Co. KGHostingIPv49
AS29169GANDI SASHostingIPv4 IPv66
AS50304Blix Solutions ASUnclassifiedIPv46
AS3216PJSC "Vimpelcom"MobileIPv43
AS3741Dimension DataUnclassifiedIPv43
AS4657StarHub LtdResidentialIPv43
AS12552GlobalConnect ABUnclassifiedIPv43

All 20 upstreams →

Transit

Downstream networks

inferred

Networks for which AS6717 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 20

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6168
AS3257GTT Communications Inc.TransitIPv4 IPv678
AS6939Hurricane Electric LLCTransitIPv424
AS34549meerfarbig GmbH & Co. KGHostingIPv49
AS29169GANDI SASHostingIPv4 IPv66
AS50304Blix Solutions ASUnclassifiedIPv46
AS3216PJSC "Vimpelcom"MobileIPv43
AS3741Dimension DataUnclassifiedIPv43
AS4657StarHub LtdResidentialIPv43
AS12552GlobalConnect ABUnclassifiedIPv43

All 20 adjacent →

Provenance

Where this comes from

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