asn.dev

Observed topology

AS206067 H3GUK

Residential RIPE

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

Transit

Upstream networks

All 24

Networks observed carrying traffic for AS206067: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv63,835
AS25135Vodafone LimitedMobileIPv4 IPv63,243
AS174Cogent Communications, LLCTransitIPv4 IPv61,121
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6886
AS50304Blix Solutions ASUnclassifiedIPv4504
AS33891Core-Backbone GmbHHostingIPv4 IPv6490
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv6324
AS24482SG.GSHostingIPv4 IPv6324
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv6324
AS48185team.blue NVUnclassifiedIPv4 IPv6324

All 24 upstreams →

Transit

Downstream networks

inferred

Networks for which AS206067 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 24

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv63,835
AS25135Vodafone LimitedMobileIPv4 IPv63,243
AS174Cogent Communications, LLCTransitIPv4 IPv61,121
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6886
AS50304Blix Solutions ASUnclassifiedIPv4504
AS33891Core-Backbone GmbHHostingIPv4 IPv6490
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv6324
AS24482SG.GSHostingIPv4 IPv6324
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv6324
AS48185team.blue NVUnclassifiedIPv4 IPv6324

All 24 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-18 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.