Resolved after 6 minutes, affecting Incoming and Team API and 1 more, on October 15, 2026.
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 • Some /v1/send API requests and SMTP submissions 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. • Some webhook deliveries and status updates (such as delivery events) may have been delayed. • No data was lost or corrupted, and messages accepted before or after this window were not affected. 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.
Affected components
Update timeline
- investigating Oct 15, 2026, 06:29 PM UTC
We are investigating intermittent server errors affecting the platform. We will keep you posted once we know more.
- resolved Oct 15, 2026, 06:36 PM UTC
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 • Some /v1/send API requests and SMTP submissions 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. • Some webhook deliveries and status updates (such as delivery events) may have been delayed. • No data was lost or corrupted, and messages accepted before or after this window were not affected. 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.
Your product runs on more than Lettermint
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