On 19 April 2026, between 06:16 and 11:44 UTC, the public API returned errors on every Cassandra-backed request. A Cassandra container log was growing unbounded because Docker log rotation wasn't configured, and it eventually filled the disk on a database node. That tripped Cassandra's stop-on-disk-failure policy and took the database offline.
We truncated the log, restarted Cassandra, and rolled the API pods to recover. Since then we've added Docker log rotation, silenced the noisy logger, and installed a daily cron that truncates any runaway container log as a safety net.
We're sorry it took as long as it did to get on top of this one. We're setting up alerting for this class of failure that bypasses do-not-disturb so it can't happen again. Thanks for flying Fluxer.
