Resolved
On October 17, 2026, during the early UTC hours, our primary database cluster experienced a cascading node failure that disrupted cluster quorum. To ensure complete data consistency, built-in safety controls temporarily suspended database operations while nodes re-established consensus. This resulted in intermittent service unavailability across several dependent components for approximately one hour.
Customers may have encountered connection timeouts, error messages, or brief service outages across platform features during the 60-minute disruption window.
Oct 22, 7:46 AM