Prismatic incident
Increased error rates in Execution Pipeline (US Commercial)
Prismatic experienced a minor incident on March 10, 2026 affecting Integration Runner, lasting 6h 47m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Mar 10, 2026, 06:49 PM UTC
At approximately 17:30 UTC, the Prismatic team received alerts via monitoring and alerting for elevated error rates in the execution pipeline for the US commercial (us-east-2) region. We are actively investigating the root cause and will provide updates as our investigation progresses.
- investigating Mar 10, 2026, 06:49 PM UTC
We are continuing to investigate this issue.
- investigating Mar 10, 2026, 07:20 PM UTC
We are continuing to investigate this issue.
- investigating Mar 10, 2026, 07:54 PM UTC
We are continuing to investigate this issue.
- investigating Mar 10, 2026, 08:55 PM UTC
We are continuing to investigate this issue.
- investigating Mar 10, 2026, 10:03 PM UTC
We are continuing to investigate and mitigate the issue. We will provide further updates as our investigation progresses.
- identified Mar 10, 2026, 11:30 PM UTC
We have identified the cause of the issue impacting performance in the US Commercial (us-east-2) execution pipeline and are actively working on a resolution. We will continue to provide updates.
- monitoring Mar 10, 2026, 11:52 PM UTC
We have identified and mitigated the issue affecting the execution pipeline in the US commercial (us-east-2) region. All metrics have returned to normal operating levels. We will continue to monitor the situation.
- resolved Mar 11, 2026, 01:36 AM UTC
This incident has been resolved.