Resolved after 26 minutes, on April 14, 2026.
Communities experienced approximately 27 minutes of downtime starting at 9:50 PM EDT. The primary database crashed and went fully offline. Our infrastructure team performed a manual failover to a standby database in a different availability zone to restore service. The crash was caused by an AWS RDS bug that we had already escalated to AWS support. We are working with AWS to prevent recurrence and have additional monitoring in place to detect database instability earlier.
Update timeline
- investigating Apr 14, 2026, 01:50 AM UTC
We are currently investigating this issue.
- resolved Apr 14, 2026, 02:17 AM UTC
This incident has been resolved.
- postmortem Apr 15, 2026, 08:05 PM UTC
Communities experienced approximately 27 minutes of downtime starting at 9:50 PM EDT. The primary database crashed and went fully offline. Our infrastructure team performed a manual failover to a standby database in a different availability zone to restore service. The crash was caused by an AWS RDS bug that we had already escalated to AWS support. We are working with AWS to prevent recurrence and have additional monitoring in place to detect database instability earlier.
Your product runs on more than Circle.so
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