Störungsverlauf von Mailtrapio

We've now resolved the incident. Thanks for your patience.

Pingdom says we are back online.

Pingdom says we are back online.

Pingdom says we are back online.

Pingdom says we are back online.

Pingdom says we are back online.

Pingdom says we are back online.

We've now resolved the incident. Thanks for your patience.

We've now resolved the incident. Thanks for your patience.

Between 11:09 and 12:11 UTC, requests using newly created API tokens or newly added domains could intermittently fail via the Email API and SMTP. Some SMTP health checks on ports 587 and 2525 also failed briefly. Existing senders and ongoing bulk/campaign sends were largely unaffected. A subset of demo and forwarded emails experienced delays. **What happened** A database change shipped without the required indexes, causing slow queries and timeouts in token validation and SMTP health checks. New tokens and domains were most affected. **What we fixed** We added the missing indexes and verified recovery. All health checks are passing and delivery is operating normally.

Some sandboxes (created 2+ years ago) could have experienced an issue with authentication resulting in "535 5.7.0 The email limit is reached." response, even if the limit was not reached. The issue causing such response has been fixed.

Spamhaus provided an update on their side https://spamhausstatus.com/pages/incident/67365d33281978053cb3db43/6846a6ff29968c05d906d38c

Pingdom says we are back online.

Pingdom says we are back online.

Pingdom says we are back online.

We've now resolved issue. Thanks for your patience.

Pingdom says we are back online.