Observed topology

AS198781 G3NS Connect Managed Services (UK) Limited

Unclassified RIPE

Upstreams 25 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 25

Adjacent (IPv6) 5

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

Transit

Upstream networks

All 25

Networks observed carrying traffic for AS198781: 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
AS6939	Hurricane Electric LLC	Transit	IPv4	1,373
AS3491	PCCW Global (HK) Ltd.	Transit	IPv4	136
AS1299	Arelion Sweden AB	Transit	IPv4	96
AS174	Cogent Communications, LLC	Transit	IPv4	67
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	60
AS24482	SG.GS	Hosting	IPv4 IPv6	30
AS37721	Virtual Technologies & Solutions	Residential	IPv4 IPv6	23
AS48185	team.blue NV	Unclassified	IPv4 IPv6	23
AS3741	Dimension Data	Unclassified	IPv4	21
AS37100	SEACOM Limited	Unclassified	IPv4	20

All 25 upstreams →

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS8791	Kerv Experience Limited	Unclassified	IPv4	162

Adjacency

Adjacent networks

All 26

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	1,484
AS8791	Kerv Experience Limited	Unclassified	IPv4	162
AS3491	PCCW Global (HK) Ltd.	Transit	IPv4	136
AS1299	Arelion Sweden AB	Transit	IPv4	96
AS174	Cogent Communications, LLC	Transit	IPv4	82
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	69
AS24482	SG.GS	Hosting	IPv4 IPv6	33
AS3741	Dimension Data	Unclassified	IPv4	24
AS37100	SEACOM Limited	Unclassified	IPv4	23
AS37721	Virtual Technologies & Solutions	Residential	IPv4 IPv6	23

All 26 adjacent →

Provenance

Where this comes from

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