Systems Status

API
operational Updated Oct 25, 11:09 UTC
DNS
operational Updated Oct 25, 11:09 UTC
Inbound SMTP
operational Updated Oct 25, 11:09 UTC
Outbound SMTP
operational Updated Oct 25, 11:09 UTC
Web Interface
operational Updated Oct 25, 11:09 UTC

✓ All Systems Operational

Recent Incidents

tx01.kfront.net Round-trip SMTP sending node is being rebooted for emergency maintenance

A critical security patch is being applied to the underlying hardware this instance runs on. Should be back up in a matter of minutes.

Started: Oct 16, 2026 02:25 UTC

Oct 16, 03:30 UTC
Took longer than anticipated. All systems are back online.

Emergency maintenance: Host reboots

We are performing brief rolling restarts across select backend servers to apply required infrastructure and host-level maintenance. Impact: Automated checks and tests may experience brief delays of a few minutes while instances cycle. You may also notice temporary status indicator changes on this dashboard as services restart. No data loss or extended disruption is expected. We anticipate all services will be fully operational shortly.

Started: Sep 28, 2026 15:17 UTC

Sep 28, 15:38 UTC
Reboots have been completed. Monitoring statistics closely, but everything appears to be working at this time.

API node balancer experiencing increased error rates

Some internal alarms have triggered showing increased connection errors on the API's node balancer. We are currently investigating.

Started: Sep 16, 2026 01:38 UTC

Sep 16, 01:43 UTC
Everything seems to have stabilized already. We will continue to monitor and update if necessary.

Alerts not resetting properly

We are aware of an issue impacting alerts clearing after they are triggered. The process is repeatedly attempting to clear the alerts, but is being prevented by a database error. This could possibly cause alerts that are already active to repeat as the alert fails to clear. We are working on a fix and hope to have it cleared up soon.

Started: Jul 29, 2026 02:43 UTC

Jul 29, 03:16 UTC
Alerts are resetting normally again. The database issue has been fixed.

Single MX server unresponsive

We have one of our primary mx servers not responding. It seems to be hung at a hardware level. We have removed it from our DNS MX record list and are working with the vendor to resolve the issue. This could have caused some temporary delays while attempting deliveries to this server.

Started: May 26, 2026 23:16 UTC

May 26, 23:38 UTC
The server issue has been resolved by our hosting provider. Everything should be back to normal.
May 27, 10:28 UTC
The MX server with hardware failure was still rejecting a certain portion of messages. This caused delays mostly coming from Microsoft servers. We are currently investigating and have removed the server from our MX pool again.
May 27, 15:07 UTC
After a thorough investigation the root cause of the rejected messages was determined to be a simple disk space issue for the message queue. During the hardware failure the disk was filled with errors, but enough space remained to process some messages while rejecting others depending on the volume of inbound messages. To compound the issue the internal alerting had been erroneously paused for an excessive duration while the initial hardware replacement was done. Once completed the internal alerting should have been reactivated, but wasn't. This would have alerted us immediately to the problem. We are reviewing the procedures concerning the internal alerting.