Country
—
ASN LANDING PAGE
ATHEEB-AS Etihad GO Company For communications
Last updated · Jul 20, 2026
Country
—
Total prefixes
325
IPv4 prefixes
186
IPv6 prefixes
139
ATHEEB-AS Etihad GO Company For communications currently reports 325 prefixes and 57 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.
ATHEEB-AS Etihad GO Company For communications is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.
The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.
Detailed data for this ASN is not available right now.
AS6939
AS6939
—
AS174
AS174
—
AS48237
AS48237
—
AS5511
AS5511
—
AS3356
AS3356
—
AS39386
AS39386
—
AS213473
AS213473
—
AS214329
AS214329
—
AS6461
AS6461
—
AS35280
AS35280
—
AS34549
AS34549
—
AS34019
AS34019
—
AS34927
AS34927
—
AS5405
AS5405
—
AS35625
AS35625
—
AS13030
AS13030
—
AS33891
AS33891
—
AS34177
AS34177
—
AS8298
AS8298
—
AS24482
AS24482
—
AS29691
AS29691
—
AS6057
AS6057
—
AS12859
AS12859
—
AS25091
AS25091
—
AS39351
AS39351
—
AS14840
AS14840
—
AS8758
AS8758
—
AS20485
AS20485
—
AS12779
AS12779
—
AS24961
AS24961
—
AS137409
AS137409
—
AS35753
AS35753
—
AS41327
AS41327
—
AS199524
AS199524
—
AS553
AS553
—
AS1103
AS1103
—
AS31510
AS31510
—
AS35360
AS35360
—
AS3212
AS3212
—
AS3214
AS3214
—
| Prefix | Name | Country |
|---|---|---|
| 185.139.123.0/24 | AS47794 | — |
| 188.248.0.0/15 | AS47794 | — |
| 188.248.1.0/24 | AS47794 | — |
| 188.248.104.0/21 | AS47794 | — |
| 188.248.112.0/21 | AS47794 | — |
| 188.248.228.0/24 | AS47794 | — |
| 188.248.229.0/24 | AS47794 | — |
| 188.248.230.0/24 | AS47794 | — |
| 188.248.232.0/22 | AS47794 | — |
| 188.248.232.0/24 | AS47794 | — |
| 188.248.240.0/24 | AS47794 | — |
| 188.248.248.0/24 | AS47794 | — |
| 188.248.249.0/24 | AS47794 | — |
| 188.248.250.0/24 | AS47794 | — |
| 188.248.251.0/24 | AS47794 | — |
| 188.248.252.0/24 | AS47794 | — |
| 188.248.253.0/24 | AS47794 | — |
| 188.248.255.0/24 | AS47794 | — |
| 188.248.31.0/24 | AS47794 | — |
| 188.248.96.0/19 | AS47794 | — |
| 188.248.96.0/21 | AS47794 | — |
| 188.249.216.0/21 | AS47794 | — |
| 2a02:888:4000::/34 | AS47794 | — |
| 2a02:888:400::/48 | AS47794 | — |
| 2a02:888:600::/46 | AS47794 | — |
| 2a02:888:600::/48 | AS47794 | — |
| 2a02:888:8000::/34 | AS47794 | — |
| 2a02:888:8000::/48 | AS47794 | — |
| 2a02:888:80da::/48 | AS47794 | — |
| 2a02:888:80fa::/48 | AS47794 | — |
| 2a02:888:8500::/48 | AS47794 | — |
| 2a02:888:99d0::/48 | AS47794 | — |
| 2a02:888::/29 | AS47794 | — |
| 2a02:888::/32 | AS47794 | — |
| 2a02:888::/33 | AS47794 | — |
| 2a02:888::/34 | AS47794 | — |
| 2a02:888::/46 | AS47794 | — |
| 2a02:888::/48 | AS47794 | — |
| 2a02:888:da::/48 | AS47794 | — |
| 2a02:888:dd0::/48 | AS47794 | — |
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
AS47794 is an autonomous system number. The current source associates it with ATHEEB-AS Etihad GO Company For communications and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
They help explain the scale, interconnection depth, and route structure of AS47794. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
Open a concrete IP page to check how the address maps into AS47794, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.