All Systems Operational

Elevated latency on port 2525 (Lab) due to a misconfigured load balancer rule following a routine infrastructure update. Inbound message queuing was delayed but no messages were lost. The issue was identified within 12 minutes of the first alert and resolved by rolling back the configuration change. A post-incident review has been completed and the load balancer rollout procedure has been updated.

New domain DKIM record verification experienced delays of up to 3 hours due to a cascading DNS propagation issue with our verification service provider. Customers attempting to verify new sending domains during this window experienced delays. Existing verified domains were unaffected. The DNS provider has since confirmed root cause and deployed a fix to their anycast infrastructure.

Intermittent 500 errors in the sending panel (app.hosted.postmta.com) caused by a failed deployment of a database connection pooler update. API functionality remained fully operational; only the web dashboard was affected. Approximately 4% of dashboard page loads were impacted. Root cause was identified as an incompatibility between the pooler version and Supabase's connection pooling configuration. Rollback completed within 22 minutes.