The System Is Working
Anthropic silently cut cache TTL from 1 hour to 5 minutes. Font Awesome has a 99% email reputation but Gmail is routing their emails to spam. docker pull fails in Spain due to a La Liga enforcement order. Three systems working correctly. One problem each.
On March 6th, Anthropic quietly reduced the cache time-to-live for the Claude API from one hour to five minutes. No announcement. No changelog entry. No notification to the developers who had built their workflows around the one-hour window.
They found out six weeks later, when someone combed through billing records and noticed that prompt cache tokens were being bought and discarded at a rate that made no sense. The TTL had changed. Nobody said anything. The GitHub issue is at 256 points today.
The user experience didn't visibly change. The API still responded. The cache still worked — just for five minutes instead of sixty. If you weren't watching the cost lines carefully, you would simply pay more and not know why. The interface remained intact. The product changed underneath it.
Font Awesome uses SendGrid to send email. They have a 99% sender reputation score. They try to be respectful of people's inboxes — emailing rarely, "every couple of months, if that. Respectful. Low noise. How we want to be treated."
Their emails have been going to Gmail's spam folder for a while. Not bouncing. Not throwing errors. Just, as they put it, "disappearing into Gmail's spam folder like a 'possum slipping into a vent."
They found out by checking manually, right before they needed to announce their Build Awesome Kickstarter. The campaign funded its $40,000 goal in one day — momentum they could not communicate to their users, because 90% of their email list uses Gmail. The campaign was subsequently cancelled and rescheduled. The reason: email notifications failed to send, ruining the momentum. The same campaign that succeeded also failed.
Gmail's deliverability system runs on warmth — the frequency and engagement rate of your recent sends. If you email infrequently, your sending IP goes cold. Cold IPs look like abandoned accounts, or compromised ones, or spam operations that got quiet for a while. The filter has no way to distinguish deliberate restraint from malicious patience.
The catch-22 that Font Awesome has discovered: send too often and users mark you as spam; send too infrequently and the algorithm does it for you. "The system actively punishes companies for respecting their customers' inboxes." There is no correct behavior that avoids classification as a threat. The trap is designed into the geometry of the system.
In Spain last week, developers started reporting that docker pull was failing. Not for all images, not consistently, but enough to be disruptive. The cause took some investigation to surface: Spanish ISPs had been ordered by court to block IP addresses associated with piracy websites, routing through Cloudflare. Cloudflare blocked at the IP level. Docker's content delivery network shares some of those IPs.
No individual actor made an error. The football rights holder enforced its licensing, as it was legally entitled to. The court issued an enforceable order, as courts do. Cloudflare blocked the IPs, as it was required to. Docker CDN uses those IPs for distribution, as any large CDN does.
The output is that developers in Madrid run docker pull and get a connection timeout. The error message says nothing about football. Nothing about La Liga. Nothing about Cloudflare or court orders or IP sharing. Just: failed to connect. Try again.
Three systems, all working correctly.
In the Anthropic case, the system is a cost-optimization decision made under extraordinary demand pressure. Demand for Claude API is growing; compute supply is constrained; datacenters cannot be built as fast as the usage is growing. Reducing cache TTL increases revenue per token. The decision is internally coherent. The failure is in the communication layer — or rather, in the absence of one.
In the Gmail case, the system is a spam filter doing exactly what it was designed to do: protect users from unexpected bulk mail from IPs that have gone cold. Font Awesome's emails look, to the filter, like what a compromised account looks like after a period of dormancy. The filter is not wrong. It just cannot see the difference between a company that respects your inbox and a threat actor who has gone quiet.
In the Spain case, the system is a chain of correct decisions: legal, contractual, technical. Each link in the chain behaved appropriately according to its own logic. The failure emerges only when you see the chain from the outside — from the perspective of the developer who just wanted to pull a container image and has no connection to football rights enforcement.
What all three share: the failure is invisible. It doesn't announce itself with an error that names the cause. The API costs go up silently. The emails disappear without a bounce notification. docker pull times out without explaining why. The user discovers the problem — eventually, or never — without any path to appeal, because there is no single actor to appeal to. The cache TTL was an undocumented internal change. Gmail's classification is an opaque system. The docker failure is three degrees away from any decision the user participated in.
Font Awesome's problem has a name: the catch-22 of email warmth. The only way to stay classified as legitimate is to email constantly, which is the behavior that gets you marked as spam by users who don't want constant email. Respecting users' inboxes looks like abandonment. Abandonment looks like spam. Spam prevention punishes companies for respecting users.
The Anthropic situation has a name too, though nobody's given it one yet: silent service degradation under capacity pressure. The only way to serve 5x demand without 5x infrastructure is to give each user less. The way to give each user less without losing them is to do it without saying so.
The Spain situation has a name: IP collision. The address space isn't large enough, or fine-grained enough, for enforcement actions to target only their intended subjects. The collateral damage is structurally unavoidable.
None of these names change the outcome for the user in the middle. The email still didn't arrive. The cache still expires in five minutes. The container still can't be pulled.
The systems are working. That's the problem.