Resolved after 30 minutes, on April 20, 2026.
This morning (between approximately 10:10 and 10:40 UTC), we experienced a performance degradation of email ingress and egress in our Dublin2 and Dublin3 clusters. This issue was brought to our attention by automated alerting built on our internal observability tooling. Application scaling policies increased capacity during this period, reducing its overall length. This was a repeated issue, seen previously on 16th March, caused by abnormally expensive processing of a set of malformed emails sent to a large number of recipients. Mitigation steps we have taken so far have unfortunately not been sufficient to avoid a recurrence, and as such, we will continue to investigate to improve resilience.
Update timeline
- resolved Apr 20, 2026, 12:06 PM UTC
This morning (between approximately 10:10 and 10:40 UTC), we experienced a performance degradation of email ingress and egress in our Dublin2 and Dublin3 clusters. This issue was brought to our attention by automated alerting built on our internal observability tooling. Application scaling policies increased capacity during this period, reducing its overall length. This was a repeated issue, seen previously on 16th March, caused by abnormally expensive processing of a set of malformed emails sent to a large number of recipients. Mitigation steps we have taken so far have unfortunately not been sufficient to avoid a recurrence, and as such, we will continue to investigate to improve resilience.
Your product runs on more than SEDNA
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