What It Means
- Pax Silica’s own architects asked the Philippines to place the New Clark City hub under US jurisdiction with diplomatic immunity for American personnel, and BCDA confirmed on record that Manila refused.
- The coalition’s point man has already fought publicly with the New York Times over corrections to the coalition’s own funding figures, undercutting confidence in the numbers cited to justify the project.
- A fellow signatory’s data centers were deliberately struck in wartime for the first time in recorded history, a documented precedent directly relevant to any Philippine data center ambitions tied to the hub.
- The friction is not confined to the Philippines. Founding members with far more capital and standing than Manila are showing comparable caution about what the coalition actually delivers.
- None of this has been weighed against the optimism driving the Philippine government’s public messaging about the project.
New Clark City’s marker unveiling in May came with a detail that never made the celebratory coverage. The United States asked the Philippines to place the entire 1,619 hectare hub under American jurisdiction, with diplomatic immunity for US personnel on site. BCDA said no. That single episode says more about how Pax Silica actually functions than any of the ceremony that followed it.
Manila Turned Down the First Real Test
Joshua Bingcang, BCDA’s president and chief executive, told reporters plainly on May 18 that Washington had requested the hub operate under American law with immunity protections equivalent to those of an embassy. “That’s their request, but we did not agree to that,” he said. Two Philippine laws now govern the arrangement instead, the Special Economic Zone Act and the Bases Conversion and Development Act, with the Department of Justice confirming the site will be treated as a regular business development contract.
A week later, Under Secretary Jacob Helberg pushed back publicly, saying his remarks on immunity had been “taken out of context” and that the goal was investor certainty, not diplomatic protection. The State Department, asked directly by Philstar to reconcile Helberg’s account with Bingcang’s, declined to address the contradiction. That refusal to clarify is itself informative. The two governments cannot agree in public on what was actually proposed, months after the request was made and rejected.
This matters because it is the first concrete test of what Pax Silica membership actually asks of a smaller signatory, and the answer was more aggressive than the coordination language in the coalition’s founding declaration suggested. If the opening request was jurisdiction and immunity, the terms still under negotiation deserve more scrutiny than they are currently getting in Philippine coverage.
The Coalition’s Own Numbers Are Already Disputed
Confidence in a project depends partly on confidence in its stated scale.
In March, Helberg accused the New York Times of fabricating quotes and misreporting the size of the Pax Silica investor consortium. The Times issued multiple corrections, adjusting a reported four trillion dollar figure down to one trillion and clarifying that the number referred to assets under management by member sovereign wealth funds, not committed investment.
A separate announcement months later cited a four trillion dollar figure again, tied to a related fund structure. Whichever figure is accurate, the public confusion over basic scale, argued about by the coalition’s own point man and one of the world’s most scrutinized newsrooms, is not something Philippine officials citing Pax Silica’s scale should treat as settled.
A Founding Member’s Infrastructure Already Became a Target
In March, Iranian drones struck two Amazon Web Services data centers in the United Arab Emirates and a third facility in Bahrain, the first time in recorded conflict that commercial data centers were deliberately targeted from the air. The strikes knocked out banking, payments, and enterprise systems across the region. Iran’s Revolutionary Guard said the facilities were struck to disrupt infrastructure supporting military and intelligence operations, and Iranian state media later named eighteen US technology companies as legitimate targets.
This is not a hypothetical risk analysts are inventing for the Philippine hub. It is a documented outcome that already happened to a fellow Pax Silica member’s digital infrastructure, in the same window the coalition was being built out. Any Philippine data center capacity eventually tied to the New Clark City hub inherits that precedent, not as a remote scenario but as a proven wartime tactic.
The Pattern Across Members, Side by Side
| Signatory or partner | What happened | What it shows |
|---|---|---|
| Philippines | Rejected a US request for jurisdiction and diplomatic immunity over the hub site | Even a founding physical host can push back on the coalition’s opening terms |
| United Arab Emirates | Had allied data centers deliberately struck during the Iran conflict | Physical infrastructure tied to the coalition carries real wartime exposure |
| United States itself | Publicly disputed its own coalition’s funding figures with a major newspaper | The scale being cited to justify the project is not settled even among its authors |
Manila’s Position Is Weaker Than the Founding Members Showing Caution
Founding members like Japan, South Korea, and the Gulf states joined Pax Silica with either deep manufacturing expertise or sovereign capital exceeding a trillion dollars each. That gives them room to push back on unfavorable terms without much risk of losing the relationship entirely. The Philippines joined with land, mineral reserves, and a hub still years from operational. Manila already showed it is willing to refuse specific demands, which is a good sign. But refusing one request is different from having the standing to renegotiate the full terms broadly if what gets finalized turns out to favor the American side more than the messaging currently suggests.
FAQ
Did the Philippines actually reject a request from Pax Silica’s organizers?
Yes. BCDA president Joshua Bingcang confirmed on May 18 that the US requested the New Clark City hub operate under American jurisdiction with diplomatic immunity, and that the Philippines refused.
Has the US disputed this account?
Yes. Under Secretary Jacob Helberg said a week later that his remarks on immunity were taken out of context, though the State Department has not directly reconciled his account with Bingcang’s.
Have other Pax Silica members faced problems with the initiative?
Yes. A fellow signatory’s commercial data centers were struck in an armed conflict, and the coalition’s own funding figures have been publicly disputed between US officials and international media.
Does this mean the Philippines should leave Pax Silica?
The reporting does not support that conclusion. It supports treating the coalition’s terms, once finalized, with the same scrutiny Manila already applied when it rejected the jurisdiction request.
What should investors and locators watch for next?
The still unsigned agreement between Manila and Washington, expected before the end of 2026, which will determine the legal and revenue terms that the immunity dispute only partially previewed.
Manila already said no once, on the single clearest overreach the coalition has attempted so far. What it has not yet done is negotiate the full agreement against partners who, by their own public record, are already fighting each other over basic facts and absorbing real wartime damage to the infrastructure this coalition was built to protect.
More developments that reshape the operating environment in National Signal section of Hemos PH.
