Observed topology

AS206347 RANSTON-AS-1 Wessex Internet Limited

Residential RIPE

Upstreams 21 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 22

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 21

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.

AS	Network	Type	Families	Paths seen
AS3356	Level 3 Parent, LLC	Transit	IPv4	592
AS174	Cogent Communications, LLC	Transit	IPv4	340
AS6939	Hurricane Electric LLC	Transit	IPv4	259
AS61124	Marston's Telecoms Limited	Residential	IPv4	150
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	96
AS50304	Blix Solutions AS	Unclassified	IPv4	64
AS33891	Core-Backbone GmbH	Hosting	IPv4	33
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	32
AS4657	StarHub Ltd	Residential	IPv4	32
AS6797	GlobalConnect AB	Unclassified	IPv4	32

All 21 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.

AS	Network	Type	Families	Paths seen
AS196745	Datacenta Hosting Ltd	Unclassified	IPv4	332

Adjacency

Adjacent networks

All 22

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

AS	Network	Type	Families	Paths seen
AS3356	Level 3 Parent, LLC	Transit	IPv4	686
AS174	Cogent Communications, LLC	Transit	IPv4	398
AS196745	Datacenta Hosting Ltd	Unclassified	IPv4	332
AS6939	Hurricane Electric LLC	Transit	IPv4	307
AS61124	Marston's Telecoms Limited	Residential	IPv4	168
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	114
AS50304	Blix Solutions AS	Unclassified	IPv4	76
AS33891	Core-Backbone GmbH	Hosting	IPv4	39
AS3216	PJSC "Vimpelcom"	Mobile	IPv4	38
AS4657	StarHub Ltd	Residential	IPv4	38

All 22 adjacent →

Provenance

Where this comes from

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