Anthropic’s planned first Australian data center has drawn opposition or requests for a delay in 595 of 598 public submissions, according to a project filing reviewed by Reuters. Two submissions supported the Western Downs Digital Park proposal, and one was neutral.
The proposed campus sits on farmland about 250 kilometers west of Brisbane. With Anthropic as its anchor tenant and a planned computing load of 1.44 gigawatts, it would be one of Australia’s largest data centers, Reuters reported on November 20, 2026. Submissions raised concerns about water, electricity demand and prices, noise, construction traffic, housing and the development’s scale. Reuters’ report provides the submission figures; the underlying filing was not available at a stable public URL in the supplied evidence.
The submissions are non-binding, and the development remains under assessment. They signal a substantial planning and community-relations problem, not a decision to reject or delay the project.
The developer’s published answers also deserve a close reading. Its water estimates cover the first building, while the master plan allows for up to four phases. Its proposed battery system addresses rapid changes in electrical demand, but that is a different task from supplying the campus’s energy.
What the 595 submissions actually show
The combined opposition-and-delay category accounts for approximately 99.5% of submissions. That is an overwhelming result within the consultation, although it should not be read as a survey of everyone living nearby.
Reuters reported that about one-third of submissions came from people living within 200 kilometers of the site. The total also combines outright objections with requests to wait until environmental hurdles are cleared. Those positions can lead to different demands: stopping a development, changing its design, or requiring more evidence before approval.
The timing is notable. The project had received five objections during the month before Anthropic was named as its tenant on September 15. The remaining objections and delay requests arrived between that announcement and the November 11 consultation deadline, according to Reuters’ account of the public-comment log. That establishes a sharp increase after Anthropic’s involvement became public, but it cannot explain why each person submitted. Reuters
Even the filing lodged on behalf of developer Zerra DC described the submissions as raising “reasonable matters.” My reading is that the breadth of those concerns matters as much as the headline count. A response focused only on cooling water, for example, would leave electricity, road access and housing questions unanswered.
Water: an air-cooled design still needs a supply plan
Zerra DC says the data centers will use 100% air-cooled technology, avoiding water-based evaporative cooling. Under its published design, water demand would primarily come from workers’ day-to-day needs.
The proposed supply arrangements differ between construction and operation:
- During construction: processed water from nearby gas operations would be the primary source, subject to agreements and approvals.
- During operation: rainwater harvesting and on-site recycling would supply almost all demand, according to the developer.
- Contingencies: externally delivered water would come from outside the local region. Groundwater is retained only as a last-resort option requiring further investigation, water entitlements and regulatory approvals.
Those are the developer’s proposed arrangements, not demonstrated operating results. Its project website publishes these figures for the first building:
| Water measure | Developer’s current estimate |
|---|---|
| Total daily water requirement | 21 kiloliters, or 21,000 liters |
| Recycled and reused on site | 8 kiloliters per day |
| Remaining raw-water requirement, primarily treated rainwater | 13 kiloliters per day |
| Rainwater collection area | Approximately 35,000 square meters |
Avoiding evaporative cooling directly addresses one potential source of water consumption. It does not, by itself, settle whether construction supplies are secured or how the operational system would perform through extended dry conditions. Those questions depend on supply agreements, storage, demand and contingency arrangements.
The distinction between the first building and the full campus is particularly important. Readers should not apply the 21-kiloliter daily figure to the entire four-phase development. Equally, multiplying it by four would assume that every phase has the same design and demand, which the available disclosures do not establish.
The website also warns that its current water modelling may differ from the lodged development application because assumptions have been refined. That creates a document-comparison problem: the figures now promoted online may not be identical to those considered by people making submissions.
I’d look for a dated reconciliation between the application and the current water plan. That would make it easier to judge whether a concern has been answered by a design change, addressed through a new assumption, or left unresolved.
A 1.44-gigawatt load raises two separate power questions
Reuters describes 1.44 gigawatts as the planned computing load. That equals 1,440 megawatts of power.
Power measures the rate of energy use. If a load of that size ran continuously for a full year, it would consume approximately 12.6 terawatt-hours:
1.44 gigawatts × 8,760 hours = 12,614 gigawatt-hours.
That is a scale illustration, not a consumption forecast. It assumes continuous operation at the stated load, says nothing about phased occupancy, and does not establish total campus demand after supporting equipment is included.
The developer proposes an on-site battery-backed power conditioning system. It says this would smooth fluctuations as computing demand changes, improve power quality and provide short-duration energy support. The project website presents the system as a way to make the campus’s demand more stable and predictable for the network.
That addresses one grid issue: how quickly a large customer’s demand changes. Another issue is how much electricity it needs over hours, days and years.
A battery can shift energy across time and help manage short fluctuations. It does not create the energy needed to sustain a continuous computing load. Assessing that role requires details such as battery power, storage capacity and duration, alongside the project’s connection and electricity-supply arrangements.
The developer also points to approximately 5.4 gigawatts of generation and storage capacity across Western Downs. That regional figure should not be treated as spare electricity available to the project. Generation and storage have different operating constraints, and storage capacity expressed in gigawatts does not reveal how long a battery can discharge.
My view is that the battery proposal is relevant, but it cannot answer the electricity-price concern on its own. A smoother load and an affordable long-term supply are separate outcomes. The available evidence does not quantify the project’s eventual effect on household bills, and its final power configuration remains subject to approvals and project changes.
Noise, roads and housing reach beyond the server halls
Reuters reported that objectors also raised noise, road damage from construction traffic and pressure on housing. These concerns connect the AI campus to everyday regional infrastructure, even though the site is farther from suburban neighborhoods than some other Australian data center proposals.
Frequently Asked Questions
3 questions
1Has the Anthropic data center been rejected?
The project remains under assessment. The 595 objections and delay requests are non-binding submissions, not a rejection or an announced delay.