<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US">
                        <id>https://status.mxroute.com/feed</id>
                                <link href="https://status.mxroute.com/feed" rel="self"></link>
                                <title><![CDATA[MXroute Status]]></title>
                    
                                <subtitle>Status updates for MXroute mail servers</subtitle>
                                                    <updated>2026-05-17T01:14:32+00:00</updated>
                        <entry>
            <title><![CDATA[Unable to reach shadow.mxrouting.net]]></title>
            <link rel="alternate" href="https://status.mxroute.com/incident/12" />
            <id>https://status.mxroute.com/12</id>
            <author>
                <name><![CDATA[MXroute]]></name>
                <email><![CDATA[support@mxroute.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[Major Outage - shadow.mxrouting.net

The shadow.mxrouting.net server stopped responding to ping, then started again, then stopped again a few minutes later. Investigating potential network issue.]]>
            </summary>
                                    <updated>2026-05-17T01:14:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Inbound DDOS attack]]></title>
            <link rel="alternate" href="https://status.mxroute.com/incident/11" />
            <id>https://status.mxroute.com/11</id>
            <author>
                <name><![CDATA[MXroute]]></name>
                <email><![CDATA[support@mxroute.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[Major Outage - ocean.mxroute.com, friday.mxlogin.com

The ocean.mxroute.com and friday.mxlogin.com servers are experiencing a significant DDOS attack. Working on this.]]>
            </summary>
                                    <updated>2026-05-15T17:47:44+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Dovecot on Chocobo server]]></title>
            <link rel="alternate" href="https://status.mxroute.com/incident/10" />
            <id>https://status.mxroute.com/10</id>
            <author>
                <name><![CDATA[MXroute]]></name>
                <email><![CDATA[support@mxroute.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[Partial Outage - chocobo.mxrouting.net

We are performing emergency maintenance on Dovecot on the chocobo.mxrouting.net server.]]>
            </summary>
                                    <updated>2026-05-06T03:09:10+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[chocobo.mxrouting.net IMAP Postmortem]]></title>
            <link rel="alternate" href="https://status.mxroute.com/incident/9" />
            <id>https://status.mxroute.com/9</id>
            <author>
                <name><![CDATA[MXroute]]></name>
                <email><![CDATA[support@mxroute.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[Degraded Performance - chocobo.mxrouting.net

This status page is only being posted so that a postmortem can be posted under it. The time of this status is not directly relevant to the issue, as the issue was fixed immediately upon initial diagnosis and since then every waking moment has been spent analyzing logs to explain the event. For this reason, the status page was treated as a lower priority for the issue.]]>
            </summary>
                                    <updated>2026-05-01T05:22:25+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Early warning: Delayed outbound email]]></title>
            <link rel="alternate" href="https://status.mxroute.com/incident/8" />
            <id>https://status.mxroute.com/8</id>
            <author>
                <name><![CDATA[MXroute]]></name>
                <email><![CDATA[support@mxroute.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[Degraded Performance - zmta

Outbound email delays just popped up again, repeat of this morning? Looking at it. We won’t let it be delayed by much.]]>
            </summary>
                                    <updated>2026-03-24T03:25:16+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Outbound Delayed]]></title>
            <link rel="alternate" href="https://status.mxroute.com/incident/7" />
            <id>https://status.mxroute.com/7</id>
            <author>
                <name><![CDATA[MXroute]]></name>
                <email><![CDATA[support@mxroute.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[Major Outage - zmta

Currently experiencing delayed outbound email, investigating right now.]]>
            </summary>
                                    <updated>2026-03-23T13:23:11+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Crossbox SSL Certificates not renewing]]></title>
            <link rel="alternate" href="https://status.mxroute.com/incident/6" />
            <id>https://status.mxroute.com/6</id>
            <author>
                <name><![CDATA[MXroute]]></name>
                <email><![CDATA[support@mxroute.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[Degraded Performance - mail.mxlogin.com

We are seeing reports trickle in that Crossbox (mail.mxlogin.com) is not properly renewing SSL certificates for custom hostnames. If you are uncertain if this relates to you, only if you did this: https://docs.mxroute.com/docs/branding/crossbox.html

Far from everyone does that. So this means nothing to most of our customers. But for those it does mean something for, it means a fair amount. But here's the thing. This is licensed third party software and the developers appear to be going dark. Now if you're picking up what I'm putting down, my hands may be tied here on how we'll react to this soon. My recommendation would be to make other plans.

Other plans:
- Custom Roundcube URL (MUST be webmail subdomain): https://docs.mxroute.com/docs/branding/customhostnames.html
- Our one-size-fits-all Roundcube: https://webmail.mxroute.com
- Literally any email client you desire]]>
            </summary>
                                    <updated>2026-03-14T10:19:39+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Issues with Taylor server]]></title>
            <link rel="alternate" href="https://status.mxroute.com/incident/5" />
            <id>https://status.mxroute.com/5</id>
            <author>
                <name><![CDATA[MXroute]]></name>
                <email><![CDATA[support@mxroute.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[Partial Outage - taylor.mxrouting.net

Investigating server.]]>
            </summary>
                                    <updated>2026-03-05T00:46:38+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[IMAP connectivity issues]]></title>
            <link rel="alternate" href="https://status.mxroute.com/incident/4" />
            <id>https://status.mxroute.com/4</id>
            <author>
                <name><![CDATA[MXroute]]></name>
                <email><![CDATA[support@mxroute.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[Degraded Performance - chocobo.mxrouting.net

The Chocobo server saw intermittent IMAP connection failures today as one of these new-generation spammers found some really strange use case that managed to consume most available resources for the IMAP server. To put that in perspective, the limits configured for the IMAP server tend to house several thousand customers without issue, it only took 1 to break it with this use case. It's some kind of connection to warmup/cold email platforms (policy violations regardless). While the issue is resolved for now, we're continuing to monitor for any further use cases of this type and investigate what we can do to prevent this kind of distributed DOS against the IMAP server by actual customers. Why can't all threats just be external? Why can't people be normal?]]>
            </summary>
                                    <updated>2026-02-27T20:26:21+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Delayed email to Microsoft]]></title>
            <link rel="alternate" href="https://status.mxroute.com/incident/3" />
            <id>https://status.mxroute.com/3</id>
            <author>
                <name><![CDATA[MXroute]]></name>
                <email><![CDATA[support@mxroute.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[Degraded Performance - zmta

We are seeing delayed outbound email to Microsoft (outlook, hotmail, etc). This appears to be a problem with their systems, though they are reporting it as this:

"The mail server has been temporarily rate limited due to IP reputation."

That said, no one works as hard as we do to combat outbound spam, and their complaint rates are very low. Our position, until we hear otherwise from them, is that this is an error in their system.]]>
            </summary>
                                    <updated>2026-02-27T06:12:41+00:00</updated>
        </entry>
    </feed>
