Observed topology

AS206999 oakfordis Oakford Internet Services Ltd

Hosting RIPE

Upstreams 21 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 21

Adjacent (IPv6) 0

Upstream graph Who carries AS206999, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS206999 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS206999: 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
AS174	Cogent Communications, LLC	Transit	IPv4	146
AS4455	IX Reach Ltd	Unclassified	IPv4	96
AS6939	Hurricane Electric LLC	Transit	IPv4	83
AS31216	BSO Network Solutions SAS	Unclassified	IPv4	49
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	21
AS50304	Blix Solutions AS	Unclassified	IPv4	14
AS24482	SG.GS	Hosting	IPv4	8
AS3741	Dimension Data	Unclassified	IPv4	7
AS4657	StarHub Ltd	Residential	IPv4	7
AS6797	GlobalConnect AB	Unclassified	IPv4	7

All 21 upstreams →

Transit

Downstream networks

inferred

Networks for which AS206999 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 21

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

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4	146
AS4455	IX Reach Ltd	Unclassified	IPv4	96
AS6939	Hurricane Electric LLC	Transit	IPv4	83
AS31216	BSO Network Solutions SAS	Unclassified	IPv4	49
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	21
AS50304	Blix Solutions AS	Unclassified	IPv4	14
AS24482	SG.GS	Hosting	IPv4	8
AS3741	Dimension Data	Unclassified	IPv4	7
AS4657	StarHub Ltd	Residential	IPv4	7
AS6797	GlobalConnect AB	Unclassified	IPv4	7

All 21 adjacent →

Provenance

Where this comes from

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