Resolved on May 8, 2026.
Incident window: 5/7/26 8:15 PM PM PDT – 8:57 PM ET Yesterday evening, customers experienced widespread errors and timeouts when using the platform. Service has been fully restored. What happened Our primary database became overloaded under heavy concurrent activity, causing requests to stall. The system failed over standby database at 8:27 PM ET, which resolved the database issue. However, our application servers did not automatically reconnect to the new database and had to be replaced with fresh instances to restore service. Impact • Elevated errors and timeouts across the platform • Service restored progressively as new application servers came online • No data was lost Resolution Full service was restored by 8:57 PM ET and the platform has been stable since.
Other major vendors with incidents that started within 30 minutes of this one
Update timeline
- resolved May 08, 2026, 03:34 PM UTC
Incident window: 5/7/26 8:15 PM PM PDT – 8:57 PM ET Yesterday evening, customers experienced widespread errors and timeouts when using the platform. Service has been fully restored. What happened Our primary database became overloaded under heavy concurrent activity, causing requests to stall. The system failed over standby database at 8:27 PM ET, which resolved the database issue. However, our application servers did not automatically reconnect to the new database and had to be replaced with fresh instances to restore service. Impact • Elevated errors and timeouts across the platform • Service restored progressively as new application servers came online • No data was lost Resolution Full service was restored by 8:57 PM ET and the platform has been stable since.
Your product runs on more than Cadmium
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