asn.dev

Observed topology

AS206347 RANSTON-AS-1 Wessex Internet Limited

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS206347: 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, LLCTransitIPv4593
AS174Cogent Communications, LLCTransitIPv4340
AS6939Hurricane Electric LLCTransitIPv4259
AS61124Marston's Telecoms LimitedResidentialIPv4151
AS34549meerfarbig GmbH & Co. KGHostingIPv496
AS50304Blix Solutions ASUnclassifiedIPv464
AS33891Core-Backbone GmbHHostingIPv433
AS3216PJSC "Vimpelcom"MobileIPv432
AS3741Dimension DataUnclassifiedIPv432
AS4657StarHub LtdResidentialIPv432

All 22 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS196745Datacenta Hosting LtdUnclassifiedIPv4338

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4687
AS174Cogent Communications, LLCTransitIPv4398
AS196745Datacenta Hosting LtdUnclassifiedIPv4338
AS6939Hurricane Electric LLCTransitIPv4307
AS61124Marston's Telecoms LimitedResidentialIPv4169
AS34549meerfarbig GmbH & Co. KGHostingIPv4114
AS50304Blix Solutions ASUnclassifiedIPv476
AS33891Core-Backbone GmbHHostingIPv439
AS3216PJSC "Vimpelcom"MobileIPv438
AS3741Dimension DataUnclassifiedIPv438

All 23 adjacent →

Provenance

Where this comes from

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