Google rations Meta's Gemini access; Meta tells staff to economize on AI tokens
The Financial Times reports Google told Meta in March it could not deliver the Gemini capacity Meta was buying; Mark Zuckerberg's teams are now pivoting workloads to in-house Muse Spark and policing per-task token usage. Google Cloud's Q1 backlog has nearly doubled to $460 billion, several other clients have been capped to a lesser degree, and the move makes a peer-to-peer hyperscaler the first publicly disclosed customer to get put on a Gemini token diet.
CNBC · 2026-06-28 · Source ↗ ·
The Financial Times reported on Sunday that Google has been imposing limits on Meta's purchases of Gemini API capacity since around March, because Google Cloud cannot deliver the compute Meta is trying to buy. The disclosure landed in the FT's Sunday edition and was syndicated through CNBC, Bloomberg, Reuters and Dawn the same day. According to people the FT cites as familiar with the arrangement, the shortfall "disrupted and delayed some of Meta's internal AI projects," and Meta has told staff internally to be more efficient with the tokens they consume against Gemini. Other Google Cloud customers were affected to a lesser degree; Meta's exceptionally high demand made the squeeze especially acute.
The mechanics are mundane and that is exactly why the story matters. There is no contract dispute, no pricing fight, no platform-policy disagreement at the centre of it. Google looked at its forecast and told one of the world's biggest software companies that the GPUs needed to honour the order did not exist. The cap appears to have held for roughly three months by the time the FT got the story, which means Meta has been running at least one significant Gemini workload at a fraction of what its product teams asked for since the first quarter. Meta's response inside the building has been the closest thing the industry has yet seen to fuel rationing: a directive to engineers to economize per-task token usage, and a planned shift of critical workloads off Gemini and onto Meta's in-house Muse Spark model, the foundation system that Meta Superintelligence Labs has been standing up since the Alexandr Wang acquihire last summer.
Google has placed limits on Meta Platforms Inc.'s use of its Gemini artificial intelligence models because it could not provide as much computing capacity as the social media company wanted.— Bloomberg summary of the Financial Times report, June 28, 2026
Google Cloud's own Q1 2026 numbers are the right frame for reading the cap. Revenue grew 63 percent year over year to more than $20 billion in the quarter, and the cloud backlog — contracted future revenue not yet recognised — nearly doubled quarter over quarter to more than $460 billion. CEO Sundar Pichai told analysts on that call that compute constraints had prevented the cloud business from growing even faster. The Meta cap is the operational consequence of that constraint at its sharpest end. It is also the first time a hyperscaler has been publicly confirmed to be rationing access to a frontier model API to a peer hyperscaler, which is a different kind of fact than "we are running out of GPUs."
The disclosure sits inside a tight cluster of June 28 stories that all point at the same physical bottleneck. The Bank for International Settlements used its 2026 Annual Economic Report, released the same Sunday in Basel, to put an "AI bust" into the top tier of named risks to global financial stability, with hyperscaler debt and "circular financing" as exhibits. TechCrunch ran a Sunday feature calling Micron "the next Nvidia" after the memory maker's stock briefly cleared Meta and Tesla in market cap on a $41.45 billion fiscal Q3. Mark Gurman's Sunday Power On newsletter reported Apple and Microsoft both citing an "unprecedented" AI-driven memory shortage when justifying iPad, Mac and Xbox price hikes. Three different shapes of the same compute crunch landed on the same day; the FT's Google-Meta scoop is the operational one.
Meta's position in the picture is unusual. The company spent roughly $14 billion last year to bring in Alexandr Wang and a Scale AI cohort to anchor the Superintelligence Labs project, and it has committed somewhere between $115 billion and $135 billion in 2026 capex, with 7,000 workers reassigned to AI roles. The Muse Spark foundation model was built precisely so Meta would not depend on rivals' APIs for production workloads. The fact that Meta still wanted enough Gemini capacity to break Google Cloud's allocation means either Muse Spark is not yet at parity for the specific workloads in question, or Meta wanted Gemini for ablation and routing reasons even with parity. Either way, the public picture is that Meta is rationing tokens internally and migrating off Gemini at speed.
Reuters could not immediately verify the Financial Times report. Google and Meta did not respond to requests for comment outside business hours.— Reuters dispatch via Dawn, June 28, 2026
The downstream signal for everyone else is that the rationing logic is structural, not relational. If Meta — a hyperscaler customer in its own right, with a Cloud Backlog of its own and a direct corporate relationship with Google's top executives — cannot get the Gemini capacity it wants, second-tier customers should plan around the same constraint. That is part of why Sunday's Firmus / Nvidia announcement of a 360 MW DSX AI Factory in Batam, Indonesia, with 170,000 accelerators and $25 to $30 billion of projected offtake over six years, lands the way it does: it is incremental capacity aimed precisely at AI-native customers who cannot get a Google or Microsoft allocation. The competitive map for frontier inference is being redrawn around physical supply, not pricing or feature comparisons.
The cap also matters for how Google itself reports the next quarter. If Pichai again has to tell analysts that constraints capped growth, the Cloud number is going to be read through the FT story rather than the slide. Google paid SpaceX roughly $920 million a month earlier this year for "bridge" access to 110,000 Nvidia GPUs and stood up a wave of new sites; that bridge has not closed the gap fast enough to keep Meta at full draw. The fix is more buildout, and more buildout is the BIS's exact concern. The Gemini token diet at Meta is, in that frame, the first concrete piece of evidence that the demand the BIS is worried about is rationed today, not theoretical tomorrow.
Computing power constraints prevented even higher growth.— Sundar Pichai, Google CEO, on a recent Alphabet earnings call
Google rations Meta's Gemini access; Meta tells staff to economize on AI tokens
The Financial Times reports Google told Meta in March it could not deliver the Gemini capacity Meta was buying; Mark Zuckerberg's teams are now pivoting workloads to in-house Muse Spark and policing per-task token usage. Google Cloud's Q1 backlog has nearly doubled to $460 billion, several other clients have been capped to a lesser degree, and the move makes a peer-to-peer hyperscaler the first publicly disclosed customer to get put on a Gemini token diet.
CNBC · 2026-06-28 · Source ↗ ·
The Financial Times reported on Sunday that Google has been imposing limits on Meta's purchases of Gemini API capacity since around March, because Google Cloud cannot deliver the compute Meta is trying to buy. The disclosure landed in the FT's Sunday edition and was syndicated through CNBC, Bloomberg, Reuters and Dawn the same day. According to people the FT cites as familiar with the arrangement, the shortfall "disrupted and delayed some of Meta's internal AI projects," and Meta has told staff internally to be more efficient with the tokens they consume against Gemini. Other Google Cloud customers were affected to a lesser degree; Meta's exceptionally high demand made the squeeze especially acute.
The mechanics are mundane and that is exactly why the story matters. There is no contract dispute, no pricing fight, no platform-policy disagreement at the centre of it. Google looked at its forecast and told one of the world's biggest software companies that the GPUs needed to honour the order did not exist. The cap appears to have held for roughly three months by the time the FT got the story, which means Meta has been running at least one significant Gemini workload at a fraction of what its product teams asked for since the first quarter. Meta's response inside the building has been the closest thing the industry has yet seen to fuel rationing: a directive to engineers to economize per-task token usage, and a planned shift of critical workloads off Gemini and onto Meta's in-house Muse Spark model, the foundation system that Meta Superintelligence Labs has been standing up since the Alexandr Wang acquihire last summer.
Google has placed limits on Meta Platforms Inc.'s use of its Gemini artificial intelligence models because it could not provide as much computing capacity as the social media company wanted.— Bloomberg summary of the Financial Times report, June 28, 2026
Google Cloud's own Q1 2026 numbers are the right frame for reading the cap. Revenue grew 63 percent year over year to more than $20 billion in the quarter, and the cloud backlog — contracted future revenue not yet recognised — nearly doubled quarter over quarter to more than $460 billion. CEO Sundar Pichai told analysts on that call that compute constraints had prevented the cloud business from growing even faster. The Meta cap is the operational consequence of that constraint at its sharpest end. It is also the first time a hyperscaler has been publicly confirmed to be rationing access to a frontier model API to a peer hyperscaler, which is a different kind of fact than "we are running out of GPUs."
The disclosure sits inside a tight cluster of June 28 stories that all point at the same physical bottleneck. The Bank for International Settlements used its 2026 Annual Economic Report, released the same Sunday in Basel, to put an "AI bust" into the top tier of named risks to global financial stability, with hyperscaler debt and "circular financing" as exhibits. TechCrunch ran a Sunday feature calling Micron "the next Nvidia" after the memory maker's stock briefly cleared Meta and Tesla in market cap on a $41.45 billion fiscal Q3. Mark Gurman's Sunday Power On newsletter reported Apple and Microsoft both citing an "unprecedented" AI-driven memory shortage when justifying iPad, Mac and Xbox price hikes. Three different shapes of the same compute crunch landed on the same day; the FT's Google-Meta scoop is the operational one.
Meta's position in the picture is unusual. The company spent roughly $14 billion last year to bring in Alexandr Wang and a Scale AI cohort to anchor the Superintelligence Labs project, and it has committed somewhere between $115 billion and $135 billion in 2026 capex, with 7,000 workers reassigned to AI roles. The Muse Spark foundation model was built precisely so Meta would not depend on rivals' APIs for production workloads. The fact that Meta still wanted enough Gemini capacity to break Google Cloud's allocation means either Muse Spark is not yet at parity for the specific workloads in question, or Meta wanted Gemini for ablation and routing reasons even with parity. Either way, the public picture is that Meta is rationing tokens internally and migrating off Gemini at speed.
Reuters could not immediately verify the Financial Times report. Google and Meta did not respond to requests for comment outside business hours.— Reuters dispatch via Dawn, June 28, 2026
The downstream signal for everyone else is that the rationing logic is structural, not relational. If Meta — a hyperscaler customer in its own right, with a Cloud Backlog of its own and a direct corporate relationship with Google's top executives — cannot get the Gemini capacity it wants, second-tier customers should plan around the same constraint. That is part of why Sunday's Firmus / Nvidia announcement of a 360 MW DSX AI Factory in Batam, Indonesia, with 170,000 accelerators and $25 to $30 billion of projected offtake over six years, lands the way it does: it is incremental capacity aimed precisely at AI-native customers who cannot get a Google or Microsoft allocation. The competitive map for frontier inference is being redrawn around physical supply, not pricing or feature comparisons.
The cap also matters for how Google itself reports the next quarter. If Pichai again has to tell analysts that constraints capped growth, the Cloud number is going to be read through the FT story rather than the slide. Google paid SpaceX roughly $920 million a month earlier this year for "bridge" access to 110,000 Nvidia GPUs and stood up a wave of new sites; that bridge has not closed the gap fast enough to keep Meta at full draw. The fix is more buildout, and more buildout is the BIS's exact concern. The Gemini token diet at Meta is, in that frame, the first concrete piece of evidence that the demand the BIS is worried about is rationed today, not theoretical tomorrow.
Computing power constraints prevented even higher growth.— Sundar Pichai, Google CEO, on a recent Alphabet earnings call