If you are considering going you can register at sreday.com/2026-san-francisc… and get half off with code SRE50
Here's what I've been working on the past few weeks. @fidian. Benchmarking is hard, expect mistakes along the way. xitter.cf/fidian/status/20926243…
Newly released models repeatedly appear near the top on the @terminalbench 2.1 leaderboard. Are these models actually on par with frontier models on terminal tasks?
We took the top 20 models from that leaderboard and ran them on TB-fn. TB-fn reworks the same 89 tasks by adding steps, tightening requirements, or requiring more complex algorithms. It also removes opportunities for shortcut solutions and ensures verifiers check only the intended criteria.
Models that clustered together on TB-2.1 spread across more tiers on TB-fn. That leaves GPT-5.6 Sol and Opus 5 in the lead, while some others drop significantly in performance. At the same time, models work 38% harder on average in TB-fn, leading to a redrawn Pareto frontier of performance vs. cost.
The full post includes interactive figures showing how the gap for open-weight families widens. It also measures how security refusals affect scores across Anthropic, Google, and OpenAI models. Fable 5 stands out, refusing at least once on 13 of the 89 TB-fn tasks.
hubt retweeted
fuuuuuuuck, whatever undergrad research assistant submitted this summary of their team's paper to phys,org, they knocked the headline out the goddamn park
I have been saying for a while that it doesn't make sense to invest in a multi-zone cloud architecture. Today I was proven right. Imagine every cloud user builds an application that can migrate between zones in a region with 3 zones A, B, and C.
As importantly, if you really want HA, test your architecture for failover. Flip your primary and secondary sites and back and forth regularly. It's expensive and time consuming, but anything less and you won't really know if your application can survive.
I am annoyed that the AWS Well Architected framework pushes users to the multi-zone design. It's bound to end badly, though I'm sure it is great for AWS margins. status.cloud.google.com/inci…





