Twitxy Saved

Jackson Clark

Verified account This account is verified. Learn more

@HacksonClark

CS PhD Student @ UIUC

Teaching AI to fix bugs.
Chambana, IL hacksonclark.github.io Joined December 2022
290 Following 247 Followers 163 Posts

Latest posts 5

Pinned post

Jackson Clark Verified account @HacksonClark
Huge congrats to @cognition for taking the #1 spot on #SREGym! 🎉

It’s been incredible to have a front-row seat to the progress in AI SRE. Shoutout to @anhangz, @yunpark93, and @jake_rachleff for an amazing release pushing the frontier of autonomous incident response.

One step closer to a world where humans don't have to be on call. 🚀

SREGym 1.1 is out now, with 2.0 on the way to push the frontier even further.

📊 Follow the progress: sregym.com
📝 More on Devin Oncall: devin.ai/blog/introduci…
Cognition @cognition Oct 15
Introducing Devin Oncall: Devin automatically investigates alerts and bugs, helping your team diagnose and resolve production incidents.

Devin Oncall already handles thousands of alerts every day for some of the world’s largest companies. Let it become your SRE today.
View quoted post on X
3 replies 15 reposts 86 likes 7.8K views View on X
Jackson Clark Verified account @HacksonClark
Did your email go down last week? This latest Microsoft outage was rather wild. It's starting to feel like the world is imploding. The central premise of #SREGym is to see if AI can stop such outages.

As a sneak peak of SREGym 2.0, we've recreated the Outlook outage. Check it out: github.com/SREGym/SREGym/… it's currently very challenging for frontier models.

What other outages would you like to see?

Stay tuned, we have something coming after Thanksgiving 🦃
github.com Add the workspace gateway cascade problem (Microsoft 365, 12 Nov 2026) by HacksonClark · Pull... Summary A SREGym 2.0 problem that recreates the environment of Microsoft's preliminary PIR for the 12 November 2026 Microsoft 365 outage (EX1550543 / MO1550821). Design notes: docs/plans/ga...
Tianyin Xu Verified account @tianyin_xu 4d
The pre PIR of the Outlook/Microsoft outage has much more clarify. Thank you @Microsoft !

The outage is indeed a very hard one; many unfortunate events occurred at the same window.

A latent bug exhausting CPU/memory under specific load condition was deployed worldwide, with no impact for 3 months. The bug was triggered by a surge in load, caused by an unrelated failover of Teams and another unrelated loss of 14% of server capacity. The system is then badly overloaded; 80% of servers were unresponsive. Then, the isolation mechanism between fault domains didn't work (it was vague in the PIR), causing cascading failures till a global outage.

Then, the (likely automatic) recovery unsurprisingly hit the classic thundering herd effect.

In this case, root-cause analysis is on the critical path and it took more than 15 hours to figure out the latent bug and revert it (it's really a very nasty bug!)

The long recovery time is quite understandable. Given such a global outage, it has to be paced carefully.

I downloaded the report at,
tianyin.github.io/misc/prepir_mi…
View quoted post on X
0 replies 7 reposts 33 likes 4.4K views View on X
Jackson Clark Verified account @HacksonClark
I'm super excited to be presenting #SREGym tomorrow! Come say hi and see where the future of AI SRE is headed :)
Logan Kilpatrick Verified account @OfficialLoganK Oct 15
We are hosting our first "Bench Summit" to bring together people excited about pushing the frontier of benchmarking, model evals, and more.

Great benchmarks are a gating function for model progress, lots to do here!

Join us in SF: rsvp.withgoogle.com/events/bench-s…
View quoted post on X
0 replies 2 reposts 16 likes 757 views View on X