Resolved after 4 hours 54 minutes, on May 7, 2026.
We are continuing to monitor for any further issues.
Update timeline
- investigating May 07, 2026, 09:08 AM UTC
We are currently investigating this issue.
- investigating May 07, 2026, 10:19 AM UTC
We are continuing to investigate this issue.
- identified May 07, 2026, 11:20 AM UTC
We have identified the root cause as elevated queue depth and throughput saturation on the MongoDB layer, leading to processing latency. A fix is being implemented to optimize handling and restore database stability
- identified May 07, 2026, 12:06 PM UTC
Executions are running fine now. However, there is still some slowness in the execution graph generation so we might see some delay in the execution updates to show up in UI. But executions would work without any delay/slowness.
- monitoring May 07, 2026, 12:09 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring May 07, 2026, 12:12 PM UTC
A fix has been implemented and we are monitoring the system.
- monitoring May 07, 2026, 12:12 PM UTC
We are continuing to monitor for any further issues.
- resolved May 07, 2026, 12:54 PM UTC
This incident has been resolved.
Your product runs on more than Split
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