Email Delivery Infrastructure Migration and Temporary Disruption

On February 28, 2026, we migrated our email delivery to a new infrastructure provider to improve cost efficiency and long-term scalability. During a window on March 1 to 2, 2026, the new provider experienced an outbound delivery issue caused by a false positive in their spam protection system, which temporarily blocked some legitimate messages. Ticket notifications, account registration, password resets, and newsletter delivery may have been affected. The provider resolved the issue on March 2, and all email delivery is operating normally.

• Posted: Feb 28, 2026, 06:00 UTC
• Resolved: Mar 2, 2026, 18:00 UTC
• Duration: 2d 12h

Timeline

1. resolved

   Mar 2, 2026, 18:00 UTC

   This incident is resolved. All email delivery is operating normally, and the deliverability score remains 10 out of 10, with SPF passing, DKIM valid, reverse DNS valid, and no blocklist entries. No further action is required.

2. monitoring

   12:00 UTC

   The provider deployed fixes across their mail infrastructure, including corrected filtering parameters, safeguards against false-positive triggers, and normalization fixes. Email delivery has resumed normally. We have confirmed the new service is stable and have closed our previous provider subscription.

3. identified

   Mar 1, 2026, 12:00 UTC

   Our new email provider experienced a false positive in their outbound spam protection filters. This temporarily blocked some legitimate outgoing messages across their platform during a window on March 1 to 2. The cause was on the provider's infrastructure, not our configuration.

4. investigating

   Feb 28, 2026, 06:00 UTC

   On February 28, 2026, we migrated email delivery to a new infrastructure provider. SPF, DKIM, and DMARC DNS records were updated for the new service, and the deliverability score was verified at 10 out of 10. Ticket notifications, password resets, and status page alerts now route through the new provider.

Permalink: /incident/30