asn.dev

Observed topology

AS8966 Etisalat-AS EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC

Mobile RIPE NSP

Upstreams 49 carry this network
Downstreams 246 this network carries
Adjacent (IPv4) 370
Adjacent (IPv6) 86
Upstream graph Who carries AS8966, and who carries them, drawn as a map up to the transit-free core. 19 exchanges Where AS8966 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 49

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

ASNetworkTypeFamiliesPaths seen
AS8452IDDQD-ASResidentialIPv4 IPv6662
AS1299Arelion Sweden ABTransitIPv4 IPv6211
AS1273IDDQD-ASBusinessIPv4 IPv6149
AS2914NTT America, Inc.TransitIPv4130
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6129
AS6939Hurricane Electric LLCTransitIPv4128
AS7473Singapore Telecommunications LtdUnclassifiedIPv4 IPv6115
AS3356Level 3 Parent, LLCTransitIPv4 IPv6104
AS4637Telstra GlobalUnclassifiedIPv4 IPv697
AS3257GTT Communications Inc.TransitIPv4 IPv660

All 49 upstreams →

Transit

Downstream networks

All 246

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

ASNetworkTypeFamiliesPaths seen
AS5384EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv4 IPv622,900
AS5416B.S.C.UnclassifiedIPv4 IPv66,873
AS18403FPT Telecom CompanyResidentialIPv43,205
AS29357NATIONAL MOBILE TELECOMMUNICATIONS COMPANY K.S.C.P.UnclassifiedIPv4 IPv61,576
AS48728Vodafone Qatar P.Q.S.CResidentialIPv4 IPv61,498
AS17557Pakistan Telecommunication Company LimitedUnclassifiedIPv4 IPv61,497
AS54253Oracle CorporationUnclassifiedIPv4 IPv61,248
AS39273Kalaam Telecom Bahrain B.S.C.ResidentialIPv41,172
AS31898Oracle CorporationHostingIPv4 IPv61,167
AS15808IDDQD-ASUnclassifiedIPv4907

All 246 downstreams →

Adjacency

Adjacent networks

All 381

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

ASNetworkTypeFamiliesPaths seen
AS5384EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv4 IPv628,109
AS35280F5 Networks SARLHostingIPv4 IPv619,540
AS17557Pakistan Telecommunication Company LimitedUnclassifiedIPv4 IPv610,640
AS8452IDDQD-ASResidentialIPv4 IPv68,497
AS5416B.S.C.UnclassifiedIPv4 IPv68,457
AS15802Emirates Integrated Telecommunications Company PJSCUnclassifiedIPv4 IPv67,594
AS2914NTT America, Inc.TransitIPv4 IPv67,352
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv66,845
AS1299Arelion Sweden ABTransitIPv4 IPv64,551
AS48728Vodafone Qatar P.Q.S.CResidentialIPv4 IPv64,045

All 381 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.