Observed topology

AS35086 NOURGLOBAL

Unclassified RIPE

Upstreams 5 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS35086: 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
AS8966	EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC	Mobile	IPv4	61
AS35753	Etihad Salam Telecom CJSC	Unclassified	IPv4	61
AS39386	Saudi Telecom Company JSC	Unclassified	IPv4	61
AS35819	Etihad Etisalat, a joint stock company	Mobile	IPv4	60
AS174	Cogent Communications, LLC	Transit	IPv4	59

Transit

Downstream networks

inferred

Networks for which AS35086 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 AS35086 in a routing path, in either direction.

AS	Network	Type	Families	Paths seen
AS8966	EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC	Mobile	IPv4	61
AS35753	Etihad Salam Telecom CJSC	Unclassified	IPv4	61
AS39386	Saudi Telecom Company JSC	Unclassified	IPv4	61
AS35819	Etihad Etisalat, a joint stock company	Mobile	IPv4	60
AS174	Cogent Communications, LLC	Transit	IPv4	59

Provenance

Where this comes from

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