<?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-11-13T19:30:30+00:00</updated>
                        <entry>
            <title><![CDATA[Microsoft Issues]]></title>
            <link rel="alternate" href="https://status.mxroute.com/incident/37" />
            <id>https://status.mxroute.com/37</id>
            <author>
                <name><![CDATA[MXroute]]></name>
                <email><![CDATA[support@mxroute.com]]></email>

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

Microsoft has been experiencing issues today, causing an inability to deliver some mail to their platform. As of the time of this message, we have seen this error from their servers 25,068 times:

"421 4.3.2 The maximum number of concurrent server connections has exceeded a limit, closing transmission channel"

This does not mean that we are exceeding a limit in connections to them, it means they are exceeding a limit of connections they can open. As of right now, this is still ongoing. However, there is one more thing you should be aware of:

We retry these emails, and if they continue to fail we send mail to our backup relay provider (mail.baby) to attempt delivery again. Their outbound filters are more strict than ours, which can cause you to receive this bounce message:

"550 200 This message was classified as rSPAM and may not be delivered"

At this time, we cannot reliably surface to you that this was not the primary issue. The primary issue is that we sent it to mail.baby in the first place, because of our inability to deliver mail to Microsoft's servers. Your mail was not simply rejected as spam, it was just rejected from retrying a third time.]]>
            </summary>
                                    <updated>2026-11-13T19:30:30+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Vegas outage]]></title>
            <link rel="alternate" href="https://status.mxroute.com/incident/36" />
            <id>https://status.mxroute.com/36</id>
            <author>
                <name><![CDATA[MXroute]]></name>
                <email><![CDATA[support@mxroute.com]]></email>

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

Vegas, where we keep Longhorn and Acadia servers, appears to be experiencing an outage above server level. Network, power, not yet clear.]]>
            </summary>
                                    <updated>2026-11-01T18:58:12+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Delayed outbound mail]]></title>
            <link rel="alternate" href="https://status.mxroute.com/incident/35" />
            <id>https://status.mxroute.com/35</id>
            <author>
                <name><![CDATA[MXroute]]></name>
                <email><![CDATA[support@mxroute.com]]></email>

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

There is currently a high level of packet loss between our outbound filter and outbound relay, causing a delay in outbound mail. As we're babysitting it right now, we're not going to re-route outbound mail through the backup relay. We're pushing mail through a bit faster after a stall, just not quite as fast as we'd like. Working with upstream.]]>
            </summary>
                                    <updated>2026-10-22T06:29:35+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Highly unlikely to be relevant to you reading this now - london.mxroute.com is down]]></title>
            <link rel="alternate" href="https://status.mxroute.com/incident/34" />
            <id>https://status.mxroute.com/34</id>
            <author>
                <name><![CDATA[MXroute]]></name>
                <email><![CDATA[support@mxroute.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[Major Outage - london.mxroute.com

Every time I post a status update about a smaller, older server, more people think it's causing them problems than are even on that server. So unless you know for a fact that "london.mxroute.com" is the server your account is hosted on, please DO NOT assume this status update has ANY relation to ANY problem that you may be experiencing and please DO open a support ticket rather than assume that this status means we're fixing something relevant to you.

The london.mxroute.com server is experiencing some kind of hardware failure. It's not disk. It's not a data loss event (we have backups anyway, even if it were). We're working with the datacenter team to resolve it.]]>
            </summary>
                                    <updated>2026-09-27T15:46:44+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[friday.mxlogin.com server reboot]]></title>
            <link rel="alternate" href="https://status.mxroute.com/incident/33" />
            <id>https://status.mxroute.com/33</id>
            <author>
                <name><![CDATA[MXroute]]></name>
                <email><![CDATA[support@mxroute.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[Partial Outage - friday.mxlogin.com

The friday.mxlogin.com server is being rebooted. If you do not recognize that server name, this status is NOT relevant to you or your service. You should still open a support ticket if you are experiencing any problems UNLESS you know for a fact that you are on the friday.mxlogin.com server.]]>
            </summary>
                                    <updated>2026-08-28T20:58:58+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[ProtonMail is down]]></title>
            <link rel="alternate" href="https://status.mxroute.com/incident/32" />
            <id>https://status.mxroute.com/32</id>
            <author>
                <name><![CDATA[MXroute]]></name>
                <email><![CDATA[support@mxroute.com]]></email>

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

ProtonMail is experiencing an outage. We are unable to deliver mail to them at the moment. It's possible that the emails in queue may bounce back to the sender. If you get a bounce for an email sent to Proton that says "This message was classified as rSPAM and may not be delivered" that does not mean that we wouldn't have delivered it if they were online, it simply means our backup relay provider filtered it, and they filter more heavily than we do.]]>
            </summary>
                                    <updated>2026-08-27T00:15:47+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Small percentage of email seeing delays]]></title>
            <link rel="alternate" href="https://status.mxroute.com/incident/31" />
            <id>https://status.mxroute.com/31</id>
            <author>
                <name><![CDATA[MXroute]]></name>
                <email><![CDATA[support@mxroute.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[Degraded Performance - eagle.mxlogin.com, pixel.mxrouting.net, taylor.mxrouting.net, sunfire.mxrouting.net, blizzard.mxrouting.net, longhorn.mxrouting.net, safari.mxrouting.net, lucy.mxrouting.net, arrow.mxrouting.net, echo.mxrouting.net, london.mxroute.com, shadow.mxrouting.net, moose.mxrouting.net, tuesday.mxrouting.net, monday.mxrouting.net, wednesday.mxrouting.net, redbull.mxrouting.net, witcher.mxrouting.net, heracles.mxrouting.net, everest.mxrouting.net, glacier.mxrouting.net, fusion.mxrouting.net, chocobo.mxrouting.net, ocean.mxroute.com, aus.mxroute.com, banshee.mxlogin.com, friday.mxlogin.com

A small percentage of emails have been seeing minor delays this morning. It seems to be a bit of a moving target, so we're trying to figure out a root cause. I opted to select every server just as a precaution, but it never seems to occur to more than 2-3 at a time.]]>
            </summary>
                                    <updated>2026-08-25T14:53:09+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Hubspot temporarily blocked on wednesday.mxrouting.net server]]></title>
            <link rel="alternate" href="https://status.mxroute.com/incident/30" />
            <id>https://status.mxroute.com/30</id>
            <author>
                <name><![CDATA[MXroute]]></name>
                <email><![CDATA[support@mxroute.com]]></email>

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

An account farmer who created a number of Tavily accounts that I now assume to be in the 10s of thousands, and attempted to forward each one to multiple remote recipients, triggered a fleet-wide emergency when Tavily rapidly sent out a newsletter to all users. The end result of this emergency, the only part customers need to be aware of, is that Hubspot is temporarily blocked on the Wednesday server as they are currently performing the equivalent of a DDOS attack against the SMTP server.

The user has been terminated for causing this event, in direct violation of our policies, and we are monitoring to see when we can unblock Hubspot.]]>
            </summary>
                                    <updated>2026-08-25T02:58:39+00:00</updated>
        </entry>
    </feed>
