Experiencing an issue that is not shown here? Please contact our support team. Account-specific sending or deliverability issues may not be displayed on this page.
Experiencing an issue that is not shown here? Please contact our support team. Account-specific sending or deliverability issues may not be displayed on this page.
Update (15 October, 18:54 UTC): After further investigation we have narrowed the scope of this incident. Only the Sending API and SMTP Relay were affected, as intermittent errors rather than an outage, so we have changed their status to Degraded performance. We have also removed the other components we originally listed, because they were not affected. The details below reflect what we found.
---
Between 18:26 and 18:30 UTC (20:26–20:30 CEST) on 15 October, some requests to the sending API and SMTP returned errors.
What happened
One connection in the pool that links our application to the primary database ended up in a read-only state. Requests that were given this connection could not write to the database, so the send requests among them failed with a server error. All other connections kept working normally, so only part of the traffic was affected during this window.
Impact
About 170 send requests (via /v1/send and SMTP) were rejected with a temporary error. Messages from rejected requests were not accepted and not sent. Clients that retry on temporary errors will have resent them automatically. Batch sends were not affected.
A small number of webhook deliveries and status updates were delayed.
Tracking, custom domains, inbound email, the Team API and the dashboard were not affected.
No data was lost or corrupted.
Resolution
We found the affected connection and removed it from the pool. Error rates were back to normal at 18:30 UTC. We are adding a safeguard so that connections in this state are detected and replaced automatically.
If you saw failed sends during this window and your integration does not retry automatically, please resend those messages.
Our sincere apologies for the inconvenience.
Resolved
Update (15 October, 18:54 UTC): After further investigation we have narrowed the scope of this incident. Only the Sending API and SMTP Relay were affected, as intermittent errors rather than an outage, so we have changed their status to Degraded performance. We have also removed the other components we originally listed, because they were not affected. The details below reflect what we found.
---
Between 18:26 and 18:30 UTC (20:26–20:30 CEST) on 15 October, some requests to the sending API and SMTP returned errors.
What happened
One connection in the pool that links our application to the primary database ended up in a read-only state. Requests that were given this connection could not write to the database, so the send requests among them failed with a server error. All other connections kept working normally, so only part of the traffic was affected during this window.
Impact
About 170 send requests (via /v1/send and SMTP) were rejected with a temporary error. Messages from rejected requests were not accepted and not sent. Clients that retry on temporary errors will have resent them automatically. Batch sends were not affected.
A small number of webhook deliveries and status updates were delayed.
Tracking, custom domains, inbound email, the Team API and the dashboard were not affected.
No data was lost or corrupted.
Resolution
We found the affected connection and removed it from the pool. Error rates were back to normal at 18:30 UTC. We are adding a safeguard so that connections in this state are detected and replaced automatically.
If you saw failed sends during this window and your integration does not retry automatically, please resend those messages.
Our sincere apologies for the inconvenience.
Investigating
We are investigating intermittent server errors affecting the platform.
We will keep you posted once we know more.