MXroute - Notice history

All systems operational

Billing Panel - Operational

100% - uptime
Mar 2024 · 100%Apr · 100.0%May · 100.0%
Mar 2024
Apr 2024
May 2024

DirectAdmin Panel - Operational

100% - uptime
Mar 2024 · 100%Apr · 100.0%May · 100.0%
Mar 2024
Apr 2024
May 2024

IMAP - Operational

100% - uptime
Mar 2024 · 100%Apr · 100.0%May · 100.0%
Mar 2024
Apr 2024
May 2024

SMTP - Operational

100% - uptime
Mar 2024 · 100%Apr · 100.0%May · 100.0%
Mar 2024
Apr 2024
May 2024

Webmail - Operational

100% - uptime
Mar 2024 · 100%Apr · 100.0%May · 100.0%
Mar 2024
Apr 2024
May 2024

Support - Operational

100% - uptime
Mar 2024 · 100%Apr · 100.0%May · 100.0%
Mar 2024
Apr 2024
May 2024

Notice history

May 2024

Fiber cut in LA
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    Source status: https://ecogent.cogentco.com/network-status

    This may be impacting performance to our network from customers in Europe and Asia. This could result in as little as slow performance, to as much as an inability to reach our servers for some customers. Our ETA would be a mirror of Cogent's.

Safari MySQL Outage
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    MySQL is being restarted on the Safari reseller server. This disables Crossbox and Roundcube mail clients on the server, but https://webmail.mxlogin.com is still online, as are all mail services (meaning your external email clients such as Outlook, Thunderbird, etc are all working fine). We're one step closer to resolving the time it takes MySQL to restart, but we're not there yet.

    If your MX, IMAP, POP, or SMTP settings point to the Crossbox instance (mail.mxlogin.com or your own custom hostname for it), then your services will always be down if/when MySQL goes down. We have no idea why people keep doing this, we tell everyone clearly what your MX records should be, what your IMAP/POP/SMTP server is, in the email we send to new customers after ordering. Please stop doing this. Just because it works doesn't mean it provides the expected level of service.

Apr 2024

MySQL Restart on Safari Server
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    The MySQL server on the safari.mxrouting.net server requires restart to fix an issue that was impacting DirectAdmin performance. There is no way to provide an ETA on this. This harms Crossbox and Roundcube, but users can use https://webmail.mxlogin.com or their own email clients during this time. No email services or functions are impacted by this event, only webmail and some functions of DirectAdmin.

    If your MX, IMAP, POP, or SMTP settings point to the Crossbox instance (mail.mxlogin.com or your own custom hostname for it), then your services will always be down if/when MySQL goes down. We have no idea why people keep doing this, we tell everyone clearly what your MX records should be, what your IMAP/POP/SMTP server is, in the email we send to new customers after ordering. Please stop doing this. Just because it works doesn't mean it provides the expected level of service.

MySQL Restart on Safari Server
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    MySQL is being restarted on the safari.mxrouting.net server to increase it's connection limit. Unfortunately this takes a long time, and there is nothing we can do to speed it up. This impacts webmail instances other than webmail.mxroute.com.

Webmail on Safari server
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    On the safari.mxrouting.net server you are likely to run into trouble with safari.mxrouting.net/webmail as a webmail option. For the moment, we recommend using mail.mxlogin.com or webmail.mxroute.com if you need to use webmail. The presence of this status update may not indicate that safari.mxrouting.net/webmail is down when you read this, but it is expected to be intermittently available at best while we work on a permanent fix.

Outbound emails to Comcast
  • Resolved
    Resolved

    Outbound email to Comcast has been restored. Exactly 105 emails were halted by this block. We have in place significant mitigations that should begin to discourage this attacker from continuing to seek out our platform.

  • Identified
    Identified

    To mitigate a threat to our platform and IP reputation, we have temporarily disabled outbound email to comcast.net. We are working on stronger mitigation to this which does not impact legitimate email. However, the attacker is presently a few steps ahead of us.

    By all appearances, an individual who desires to send Comcast phishing emails has purchased multiple accounts from resellers, some accounts sitting dormant for as long as 4 months. We keep terminating their accounts as we identify them, but from the outside the only reasonable conclusion is that we appear to be taking no action to halt this activity on our platform. Because, to put it simply, our termination efforts have not effectively halted these outbound emails for the last 72 hours. Playing whack-a-mole may be entertaining, but we believe that it would be better for users to be unable to send email to Comcast for a few hours than any other short term option.

Mar 2024

echo.mxrouting.net
  • Resolved
    Resolved

    Bad syntax in config file after update, which was only present on the echo server. Fixed.

  • Identified
    Identified

    MySQL is down on the echo.mxrouting.net server. This is causing some webmail installations to return errors. While we work on this, feel free to use webmail.mxroute.com or mail.mxlogin.com, as well as your own email clients (Thunderbird, Outlook, Apple Mail, etc).

Mar 2024 to May 2024

Next