Increased API error rate
Around 22:52 UTC the API started returning intermittent errors. We are investigating the issue but believe it may have subsided already. An update will be made once a cause is determined.
Started: Nov 06, 2025 23:32 UTC
Nov 06, 23:56 UTC
The issue has been identified. A worker pool was failing to shutdown old workers correctly leaving them in a zombie state. After running out of slots for additional workers to be spawned it would fail on the request. This only happened on 1 of 3 servers backing the api. It has been removed from service at this time while we determine the root cause.
MX Record Processing Interruption
Approximate Incident Timeline: Start of Issue: 14:30 CT (15:30 ET / 19:30 UTC) Issue Resolved: 14:50 CT (15:50 ET / 19:50 UTC)
An MX server unexpectedly started rejecting test messages. After identifying the issue we removed the server from our MX pool and have taken it offline for further investigation. Some clients may have received alerts during this period and might notice the test messages still stuck in their queues.
Started: May 14, 2025 20:29 UTC
May 14, 21:04 UTC
Problem found: Incorrect order of operations in the systems automation restarted postfix before updating a map file causing it to read an empty map file instead of the correct information. This caused the server to reject incoming messages for mailive01, but not other addresses. Automation will be fixed and tested.
Adding round trip smtp monitors in web interface returning server error
When adding a new SMTP round trip monitor the web interface is throwing an "Internal Server Error". We are currently investigating and will update once more is known.
Started: Mar 19, 2025 20:32 UTC
Mar 19, 20:45 UTC
The problem has been identified and a fix is ready. Production will be updated in the next few hours.
Mar 20, 00:44 UTC
Production has been updated. Adding a round trip SMTP monitor no longer causes an error.
