Observed topology

AS43836 Hayat for Internet & communication LLC

Unclassified RIPE

Upstreams 0 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 4

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS43836: 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 AS43836 was observed as the last hop before the origin, meaning it appears to provide them transit.

AS	Network	Type	Families	Paths seen
AS205906	Informatics and Telecommunications Public Company (ITPC)	Unclassified	IPv4	59

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS208293	AlSalam State Company	Unclassified	IPv4	1,215
AS211181	Civilisation Information Technology, communication and internet services Co., LTD	Unclassified	IPv4	776
AS21277	Allay Nawroz Telecom Company for Communication/Ltd.	Unclassified	IPv4	498
AS205906	Informatics and Telecommunications Public Company (ITPC)	Unclassified	IPv4	59

Provenance

Where this comes from

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