Observed topology

AS212088 Al-Tair Al-Watani Company for General Trading, Agricultural Investments, Production and Distribution, Technical Services, Internet Services, Public Services, Information Technology and Software Ltd

Unclassified RIPE

Upstreams 0 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS212088: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

Networks for which AS212088 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

observed

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

AS	Network	Type	Families	Paths seen
AS208293	AlSalam State Company	Unclassified	IPv4	3,163
AS211513	Al Lawn Al Akhdar International Company for Communications and Information Technology Ltd.	Unclassified	IPv4	2,065
AS200178	Tarik Al-thuraya Company For Communications Service Ltd.	Unclassified	IPv4	872
AS213642	Coretech Bilisim Hizmetleri Sanayi Ticaret Limited Sirketi	Unclassified	IPv4	164
AS39216	Pulk Company for General Trading, Communications & Investment, Ltd.	Unclassified	IPv4	62

Provenance

Where this comes from

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