Resolved on June 5, 2025.
At approximately 7:00AM Arizona the Prismatic team received several alert notifications for failed executions. Upon investigation it was discovered that a very large volume of executions had started, and autoscaling was not configured with a high enough upper threshold to accommodate. The Prismatic team took action to raise the thresholds and align them with other high-volume stacks, and service was fully restored by 7:20AM Arizona. We will audit and address any similar situations we discover on other high-volume stacks.
Update timeline
- resolved Jun 05, 2025, 07:23 PM UTC
At approximately 7:00AM Arizona the Prismatic team received several alert notifications for failed executions. Upon investigation it was discovered that a very large volume of executions had started, and autoscaling was not configured with a high enough upper threshold to accommodate. The Prismatic team took action to raise the thresholds and align them with other high-volume stacks, and service was fully restored by 7:20AM Arizona. We will audit and address any similar situations we discover on other high-volume stacks.
Your product runs on more than Prismatic
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