After: We are seeing 502s with quay.io pushes & pulls
AddedUpdateidentified#8
Before: not present
After: The team has identified the issue and is investigating. We've shifted Quay to be read-only now so pulls should gradually begin restoring but pushes will still fail.
AddedUpdatemonitoring#9
Before: not present
After: We've implemented a fix for the issue, pushes have been restored now.
AddedUpdateresolved#10
Before: not present
After: Quay.io functionality has been restored.
AddedUpdatepostmortem#11
Before: not present
After: On March 30, 2026, Quay.io experienced a service disruption affecting image pulls and pushes, caused by an unexpected burst of resource-intensive operations that temporarily overloaded our primary database. Our engineering team mitigated the issue by failing over read traffic, restoring image pull capabilities within 45 minutes, and subsequently restored full push functionality once the database stabilized. We have since implemented enhanced traffic filtering and are actively optimizing our systems to prevent this from happening in the future.
Rewindex commits each version of an incident to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.