Claude Code Daily Benchmarks for Degradation Tracking

Re:Claude Code Daily Benchmarks for Degradation Tracking by cedws on Thursday January 29, 2026 @10:38AM (#46811604)

Agreed, this benchmark would be much more useful ran multiple times a day. That could reveal degredation in line with load patterns.

[ Parent | on HN ]

Re:Claude Code Daily Benchmarks for Degradation Tracking by bredren on Thursday January 29, 2026 @10:52AM (#46811808)

For CC, I suspect it also need to be testing and labeling separate runs against subscription, public API and Bedrock-served models?

It’s a terrific idea to provide this. ~Isitdownorisitjustme for LLMs would be the parakeet in the coalmine that could at least inform the multitude of discussion threads about suspected dips in performance (beyond HN).

What we could also use is similar stuff for Codex, and eventually Gemini.

Really, the providers themselves should be running these tests and publishing the data.

The availability status information is no longer sufficient to gauge the service delivery because it is by nature non-deterministic.

[ Parent | on HN ]

Re:Claude Code Daily Benchmarks for Degradation Tracking by swyx on Thursday January 29, 2026 @02:21PM (#46815160)

i recall another project here on HN maybe 4-6 months ago that would run tests 4x a day or something. not sure how to find them again

[ Parent | on HN ]