Minor incident

Cordial: AWS Service Impact, USW2

Current status of Cordial: Operational — live Cordial status

Timeline

1. Nov 6, 2026, 23:57 UTC
   investigating
   Degraded Performance: Delayed Message and Automation Processing Status: Monitoring Beginning at 2:51 PM PST on November 6, our cloud infrastructure provider began experiencing issues in the US West (Oregon) region. As a result, some message and automation processing is running slower than normal. No data has been lost. Delayed jobs are queued and will be processed as capacity is restored. All other platform functions, including the Admin UI, API, and event tracking, are operating normally. Our team is actively monitoring the situation. We’ll post another update within 60 minutes, or sooner if anything changes.
2. Nov 7, 2026, 00:25 UTC
   monitoring
   Our cloud infrastructure provider is recovering from an issue in the US West (Oregon) region that began at 2:51 PM PST on November 6. We’re seeing processing capacity come back, and the backlog of delayed messages and automations is working through the queue. No data has been lost. Delayed jobs will continue to process as capacity is restored, and you may still see slower-than-normal processing in the meantime. All other platform functions, including the Admin UI, API, and event tracking, remain operational. We’re continuing to monitor recovery. We’ll post another update within 60 minutes, or sooner if anything changes.
3. Nov 7, 2026, 00:38 UTC
   monitoring
   As of 4:35 PM PST, job processing has returned to normal and any delayed jobs are being worked through. Our cloud infrastructure provider hasn’t fully resolved the issue on their side yet, so we’ll keep this incident open and continue to monitor. We’ll post another update once it’s fully resolved.
4. Nov 7, 2026, 01:07 UTC
   resolved
   Our system has returned to normal operation.

Updates as published by Cordial (original).