Observed topology

AS43338 RATIONAL-AS TSG Interactive Services Limited

Unclassified RIPE

Upstreams 6 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 8

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS43338: 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
AS32787	Akamai Technologies, Inc.	Hosting	IPv4	488
AS2914	NTT America, Inc.	Transit	IPv4	46
AS174	Cogent Communications, LLC	Transit	IPv4	34
AS3320	Deutsche Telekom AG	Mobile	IPv4	21
AS3257	GTT Communications Inc.	Transit	IPv4	20
AS6762	TELECOM ITALIA SPARKLE S.p.A.	Transit	IPv4	14

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS48536	TSG Interactive Services Limited	Unclassified	IPv4	334
AS44815	TSG INTERACTIVE SERVICES (IRELAND) LIMITED	Unclassified	IPv4	61

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS32787	Akamai Technologies, Inc.	Hosting	IPv4	792
AS48536	TSG Interactive Services Limited	Unclassified	IPv4	334
AS2914	NTT America, Inc.	Transit	IPv4	69
AS44815	TSG INTERACTIVE SERVICES (IRELAND) LIMITED	Unclassified	IPv4	61
AS3320	Deutsche Telekom AG	Mobile	IPv4	55
AS174	Cogent Communications, LLC	Transit	IPv4	51
AS3257	GTT Communications Inc.	Transit	IPv4	30
AS6762	TELECOM ITALIA SPARKLE S.p.A.	Transit	IPv4	21

Provenance

Where this comes from

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