Resolved after 2 days 11 hours, affecting Product, on February 17, 2025.
Due to the database maintenance we performed on Feb 15, our database was struggling to handle operational load. We rolled back some of those changes and have prioritized work to optimize our database usage to prevent incidents like this in the future.
Affected components
Update timeline
- investigating Feb 17, 2025, 06:19 AM UTC
Vitally is experiencing an unusual amount of server timeouts. We are looking into the incident.
- identified Feb 17, 2025, 06:43 AM UTC
We have mitigated the issue, though background jobs may experience delays.
- resolved Feb 19, 2025, 06:00 PM UTC
Due to the database maintenance we performed on Feb 15, our database was struggling to handle operational load. We rolled back some of those changes and have prioritized work to optimize our database usage to prevent incidents like this in the future.
Your product runs on more than Vitally
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