Resolved after 23 hours 30 minutes, on December 10, 2025.
During a planned database migration, we experienced sustained and escalating CPU spikes on the new primary database instance shortly after cutover. Despite scaling the infrastructure, adding replicas, creating missing indexes, deploying multiple hotfixes, and engaging appropriate support, performance issues persisted—ultimately traced to an improper index strategy and heavy update/truncate activity—leading to a full rollback to restore customer performance and stability.
Update timeline
- resolved Feb 17, 2026, 08:48 PM UTC
During a planned database migration, we experienced sustained and escalating CPU spikes on the new primary database instance shortly after cutover. Despite scaling the infrastructure, adding replicas, creating missing indexes, deploying multiple hotfixes, and engaging appropriate support, performance issues persisted—ultimately traced to an improper index strategy and heavy update/truncate activity—leading to a full rollback to restore customer performance and stability.
Your product runs on more than hireEZ
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services