Prismatic Outage History

Beginning at approximately 17:59 UTC on September 22, customers across all deployment regions were unable to access the Prismatic web app. Service was fully restored across all regions at approximately 18:20 UTC. This incident has been resolved.

Beginning at approximately 20:00 UTC on September 16, customers with deployments in the US-WEST-2 region experienced increased error rates due to a disruption in underlying AWS services in that region. The underlying service recovered around 21:10 UTC.

Between 20:04 and 23:20 UTC on August 17, the OAuth2 service in eu-west-1 experienced intermittent periods of token refresh failures. The issue was corrected the same night and refreshes resumed normally.

A routine update caused a service interruption of the execution pipeline for some customers for approximately 5 minutes. A rollback was performed and service was restored. The Prismatic team is investigating the root cause and will ensure a subsequent update does not contain the same regression.

We experienced an outage impacting the Web App and Embedded UI in the GovCloud environment. The incident began at 9:19 a.m. CT on June 14, 2025 and was fully resolved at 8:02 a.m. CT on June 15, 2025. During the outage, users were unable to access the web app or embedded screens. Integration executions continued to run as expected and API access was not impacted. Commercial Cloud environments were not impacted.

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.

This incident has been resolved.

Confirmed back to fully operational status.

At approximately 8:57am CT an update to the Prismatic web application was deployed that contained updated dependencies. Unfortunately there was a misconfiguration that was not problematic in development and CI environments, but caused crashes in the production environments. The Prismatic engineering team received alerts immediately upon release that there were problems and immediately started rolling back to the previous version. Full functionality was restored by 9:30am CT. The Prismatic engineering team is investigating root cause and will properly address this issue and further investigate how to improve the test coverage so as to minimize the likelihood and impact of similar situations in the future.

This incident has been resolved.

It appears the issue has been completely resolved and AWS is working to understand the root issue(s). We will open a new issue on this status page if any further problems emerge.