We’d like to provide some transparency regarding yesterday’s unscheduled service interruption that occurred during a planned update deployment.
Yesterday, while rolling out routine application updates, our primary database experienced an unexpected failure, which triggered an emergency replacement and recovery procedure.
As a result, we experienced approximately 9 hours of downtime – our longest in quite some time.
What happened:
- During a deployment, our database crashed unexpectedly
- An immediate emergency recovery process was initiated
- The replacement and verification process took longer than anticipated due to the size and criticality of the system
- Full service was restored after approximately 9 hours
We understand the importance of availability, and we are treating this incident with the highest priority.
We are conducting a full postmortem to analyze the root cause and implement safeguards to reduce the risk of similar occurrences in the future — including additional pre-deployment validation steps and improved automated failover mechanisms.
We sincerely appreciate your patience and understanding.
If you have any further questions or require specific details related to your account, please don’t hesitate to reach out to us directly.
