MXroute - Notice history

This has been resolved for most of the day, we just wanted to give it time to be sure.

It is happening again. You can expect Crossbox to be down on the glacier.mxrouting.net server until the developers are able to address it, because this is not something we can fix. You should use an alternate webmail today if you can, like webmail.mxroute.com.

We are still waiting on a response from the developers of Crossbox. It is not within our ability to fix this while ensuring that no unnecessary problems are created from the fix.

This incident has been resolved. The cause of the initial issue was determined to be an SMTP-based DDOS attack. Nothing new for us, just a slightly new technique that should now be mitigated.

Server went unresponsive. The issues that caused it to take so long to bring it back up have been fixed, but the original cause of getting to that point wasn't clearly identified. It looks like we're identifying that now.

We have resolved this. The root cause is also resolved, ensuring that this will not happen again. At least, not the noteworthy downtime part.

We're continuing to work on this. The issue is minor, there are just really poorly timed road blocks that are slowing this down.

Email that was being queued is now being delivered, inboxes are working properly again on the longhorn.mxrouting.net server.

Postponed until a later date.

Maintenance on Taylor complete. Probably.

While we're still updating some software, the actual mail servers (SMTP, IMAP, POP) are online and functioning.

Everything has been normal for about 24 hours or so now, let's call this resolved.

It looks like everything is operating within normal parameters, but leaving this status open until we’re certain that there isn’t merely some dormant underlying cause. There shouldn’t be, but overconfidence would be a mistake.

IMAP performance "should" be a clear issue with clear paths to resolution. This one is a bit strange. There is no way to resolve it other than to test adjustments and configuration changes to the IMAP server in production, this exact issue cannot be replicated in staging when it's cause is not so apparent. However, we will continue to test changes until we get it right. While we expect it to already be better, it may take some time to be confident in that, so this status will remain open for an extended period of time regardless of the state of the issue.