Information Technology · Sunday, 16 August 2026
01 · Briefing · what happened
AI's cheapest model gets four times dearer today, and Google halves its own
DeepSeek's price rise lands today while Google's newest model runs at half price into January. The promotional era of cheap AI is ending, unevenly.
$3.96
DeepSeek's peak price per million output tokens
up from $0.87, effective today
70%
of Alphabet's quarterly profit
came from stakes in other companies, not its own trade
$129bn
business spending on cloud in one quarter
up 35% on a year earlier
1.6m
RingCentral customers exposed
the break-in began with a phone call to one employee
At a glance
- DeepSeek's flagship model costs more than four times more from today, and now charges different rates at busy and quiet hours.
- Google went the other way, pricing its new Gemini 3.7 Flash at half rate until 1 January, when it doubles.
- Google is selling fewer retries - each failed attempt by an AI agent is a bill, and cheap models made that bill invisible.
- Money kept arriving regardless: Databricks at $190bn, Cognition in talks at $40bn, Nvidia lining up $500bn for data centres.
- Over 70% of Alphabet's quarterly profit came from the rising value of its stakes in other companies, not its own business.
- A pet-feeder outage left animals unfed and the feeding records unrecoverable, so owners could not tell whether food was dispensed.
- AIG began selling insurance that pays out automatically when cloud downtime crosses a set trigger.
- A judge gave Google one week to stop making rival app stores hard to find in the Play Store.
Forces in play
DeepSeek quadruples today and Google's half-price offer expires in January; the promotional era is closing
Databricks at $190bn, Cognition at $40bn, Nvidia lining up $500bn for data centres
one company's servers went quiet and pets went unfed; insurers now sell cover for cloud downtime
Nvidia released a free model small enough for a single laptop chip, which needs no one's servers
How it unfolded
- Tuesday Petlibro's servers stop answering; scheduled feeds are missed
- Thursday Google launches Gemini 3.7 Flash at half price; AIG launches cloud-outage cover
- Friday A judge gives Google one week on the Play Store; 1.6m RingCentral records are dumped
- Today DeepSeek's fourfold price rise takes effect
Where this points
Watch whether Google's January price doubling holds when it arrives - if the introductory rates keep getting extended, the cheap era is being propped up rather than ended.
Full briefing
Two prices move in opposite directions
From today, the model that made cheap AI famous costs more than four times what it did yesterday. DeepSeek’s V4 Pro rises from $0.87 to $3.96 per million output tokens at peak hours
Off-peak, the same model costs $1.98
DeepSeek is still cheap by comparison. Moonshot’s Kimi K3 charges $15 per million output tokens and OpenAI’s most advanced model $30
Google moved the other way. Gemini 3.7 Flash arrived three weeks after 3.6 Flash, at $0.75 per million input tokens and $3.75 output
What Google is selling is worth naming, because it is the quiet cost nobody prices. The pitch for 3.7 Flash is fewer retries and less manual supervision
Nvidia pushed from the opposite end, releasing Nemotron 3.5 Lightning, a free model small enough to run on a single graphics chip in a laptop
The money arrives anyway
Databricks closed $5 billion at a $190 billion valuation
Cognition, which makes the coding agent Devin, is in talks at $40 billion, three months after raising $1 billion at $26 billion
Two people counted where that money comes from. More than 70% of Alphabet’s net quarterly income came from the rising value of its stakes in other companies, mostly SpaceX
When the thing in the middle goes quiet
On Tuesday morning, Petlibro’s servers stopped answering, and cats and dogs went unfed
The company’s position is that schedules are stored on the feeder itself and run without any internet command
The business version ran the same week. LexisNexis pulled three services offline after unusual activity on servers run by an outside supplier
Insurance has now caught up. AIG launched cover that pays out automatically when cloud downtime crosses a preset trigger, built with a firm that monitors more than 750 data centres and 9,000 software providers
The courts move on the platforms
Google began letting rival app stores be downloaded from the Play Store this month, under a 2023 antitrust loss to Epic
Meta lost its attempt to stop a separate case reaching a jury. An appeals court ruled 3-0 that the law shielding platforms from liability for user content is a defence at trial, not a blanket immunity from being sued
The break-ins started with a phone call
Attackers dumped 1.6 million RingCentral customers’ email addresses, names, addresses and phone numbers online after the company refused to pay
A quieter one reached further. Poisoned versions of a widely used AI development tool scraped credentials out of 2,500 organisations during a 40-minute window in March, including Microsoft, Amazon, Cisco, Samsung and Salesforce
Elsewhere
Accel closed a $550 million India fund in weeks, 19 months after the last one and with more than half of that still unspent
02 · Lesson · why it matters
Exactly once is a promise no network can keep
When a reply never comes back, nothing can tell you whether the thing happened or the confirmation got lost.
How it works
- One machine asks another to do something
- The reply never arrives
- The asker cannot tell if it happened or the confirmation was lost
- So it either tries again, risking twice, or stops, risking never
- The fix is not better delivery but a named request
- The same name arriving twice returns the first answer instead of acting again
The twist
Exactly once is not something a network can promise - so the only real fix is to make the action safe to repeat, not to try harder to deliver it.
Where you've seen this
Card payments
a payment that times out is either taken or not, and a careless retry charges you twice
Sending an email
you press send, the wheel spins, and you cannot tell whether it went until you check the sent folder
Ordering at a busy bar
you shout the order again over the noise and end up with two drinks
AI agents doing tasks
a tool call that hangs gets retried, and the booking is made twice
The catch
Naming a request only works if both sides agree on the name and remember it - and memory of what has already been done is itself something that can be lost.
Full lesson
The button that told you nothing
Somewhere this week, a person was away from home, tapping a button in an app to feed a cat. The button did nothing. No error, no confirmation, no food showing in the log. The company later said some records from those hours may never be recovered.
Sit with what that person actually faced. They did not know whether the cat had eaten. They could not find out. And they had one decision in front of them: press again, or don’t.
Two situations that look identical from outside
The app sent a command to a server, the server was meant to send one to the feeder, and something in that chain went quiet. Now there are two possible worlds.
In the first, the command never landed. The bowl is empty.
In the second, the command landed, the food dropped, and the message saying so got lost on the way back.
From where the owner sits, these two worlds are the same picture. Same blank screen, same silence. This is not a bug anyone forgot to fix. It is what happens whenever one machine asks another to do something over a connection neither of them owns. Silence means one of two things and never says which.
So you choose which way to be wrong
Because the ambiguity cannot be removed, a system gets exactly two honest options.
It can try again. Then the thing definitely happens, and it might happen twice. The cat gets a second breakfast. The card gets charged twice.
Or it can not try again. Then the thing definitely happens no more than once, and it might not happen at all. The cat goes hungry.
That is the whole menu. Engineers call these at-least-once and at-most-once, and there is no third item. “Exactly once” is what everybody wants and nobody can deliver. Delivering it would mean knowing which of the two worlds you are in, and that is the one thing the silence refuses to say.
The fix is not better delivery
The way real systems survive this is to stop trying to solve the wrong problem. You cannot make the message arrive reliably enough. What you can do is make the action safe to do twice.
Give the request a name before you send it. Not “feed the cat” but “feed the cat, seven o’clock Tuesday, request number 4471”. Then the receiving side keeps a list of names it has already acted on. If that name shows up again, it does not dispense more food. It replies with the answer it gave the first time.
Now the ambiguity is still there, and it no longer matters. You can retry as often as you like. The action happened once because the name was used once.
This is why your bank gives you a reference number. It is why a payment that times out and gets retried does not charge you twice when it is built properly, and why it sometimes does when it is not. The difference between those two experiences is not luck or a better connection. It is whether somebody decided the request needed a name.
Where the ambiguity gets pushed
Someone chose where the uncertainty lands. A feeder can hold its own schedule and run without asking anyone. Routing the command through a company’s servers is a design decision, and it moves the not-knowing from the machine, which could have kept a record, to the person, who cannot. When the company then says the records may be unrecoverable, the last place that could have settled the question has closed.
The same shape is being sold three ways this month, and it is worth seeing them as one thing. A model company advertising fewer retries is advertising a smaller dose of this problem. Software agents that carry out tasks alone hit it constantly, and every retry now costs real money at the new prices. An insurer selling automatic payouts for downtime has simply put a price on the fact that when the middle goes quiet, nobody can tell you what happened.
The record is held by someone else
Most of us meet this daily and never name it. The spinning wheel on a payment page. The message that may or may not have sent. The order confirmation that never arrived, and the choice to order again or wait. Each time, the question of what actually happened is answerable only by whoever built the system, from records they own and may not keep.
Nobody in that chain has certainty. The engineers do not have it either. They only get to choose which way to be uncertain, and who carries it.
03 · Lab · your turn
The Silent Button
Rehearse the choice when a reply never comes back, and feel why naming a request is the only fix.
04 · Hope · carry this
Almost nothing we depend on can promise it arrived. People built a working world on top of that anyway, one carefully named request at a time.
More from Information Technology