MXroute - Notice history

Support experiencing degraded performance

Billing Panel - Operational

100% - uptime
Aug 2025 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2025
Sep 2025
Oct 2025

DirectAdmin Panel - Operational

100% - uptime
Aug 2025 · 100.0%Sep · 100.0%Oct · 99.78%

Previous page

Next page

Aug 2025
Sep 2025
Oct 2025

IMAP - Operational

100% - uptime
Aug 2025 · 100.0%Sep · 100.0%Oct · 99.77%

Previous page

Next page

Aug 2025
Sep 2025
Oct 2025

SMTP - Operational

100% - uptime
Aug 2025 · 100.0%Sep · 100.0%Oct · 99.74%

Previous page

Next page

Aug 2025
Sep 2025
Oct 2025

Webmail - Operational

100% - uptime
Aug 2025 · 100.0%Sep · 100.0%Oct · 99.78%

Previous page

Next page

Aug 2025
Sep 2025
Oct 2025

Support - Degraded performance

100% - uptime
Aug 2025 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2025
Sep 2025
Oct 2025

Notice history

Oct 2025

taylor.mxrouting.net server not responding
  • Resolved
    Resolved

    The motherboard failed on the server. The disks had to be migrated to a new box. Everything is fine, no further issue expected.

  • Monitoring
    Monitoring

    Server is online. Waiting for postmortem from on-site techs.

  • Update
    Update

    We are continuing to wait for an update from on-site technicians.

  • Update
    Update

    Datacenter technicians have been working on the server for a bit to determine why it is inaccessible. It is not believed to be a hardware issue, this appears to be a network issue.

  • Investigating
    Investigating

    We are currently investigating this incident. This ONLY relates to the taylor.mxrouting.net server.

Performance of safari.mxrouting.net server
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating

    We are currently investigating poor performance for some users on the safari.mxrouting.net server.

IMAP on Wednesday/Taylor servers
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    We are working on a fix for this incident. It won't take long.

Outbound delivery delay
  • Resolved
    Resolved

    Mail flow fully restored. It will take a bit longer to push all of the email that was queued during this, but it is flowing.

    What happened: Our cloud provider rebooted the node without notice. Our interfaces did not come up as intended, monitoring system did not trip because BGP didn't actually go down, ZoneMTA couldn't create outbound connections. Connections from the same /24 to the same /24 no longer worked over port 2525.

    What we did: Bring interfaces up, get email flowing again. Changed postfix bind address on filter server to cloud-provided IP to compensate for failure to connect over 2525 from/to the same /24 (as this "appears" to be outside of our ability to impact). Adjusted DNS for filter006.mxroute.com for Received header reverse DNS checks. Flushed mail queue. Changed monitoring system to ping the /24 that sends mail rather than just monitor it's BGP session.

  • Monitoring
    Monitoring

    Outbound mail flow is restored, but it is taking a bit of time to get all of the queued emails out.

  • Identified
    Identified

    Outbound delivery is currently delayed on our network, working to resolve quickly.

Reduced support capacity
  • Identified
    Identified

    We currently have reduced capacity for ticket support. Please be sure that you are using our documentation, as 9 out of 10 tickets can easily be answered here: https://docs.mxroute.com

Sep 2025

No notices reported this month

Aug 2025

Some deliveries to Google were delayed
  • Resolved
    Resolved

    This morning we experienced an issue with DNS resolvers on our outbound relays which caused 13,964 outbound emails to be delayed on their path to Google/Gmail. This issue may have added anywhere from 30 seconds to 5 minutes in delay. To give you an idea of the scope of this, 68,522 emails were successfully delivered to Google/Gmail without delay during the same time period. So while it was far from every email, it was not insignificant. This has been resolved.

The whole internet just went boom
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating

    It looks like there is a massive internet routing issue at the moment. Cogent and Arelion look like the culprits from where we sit, but this is a pretty early report of the issue so take it with a grain of salt. Kind of feels like someone just fucked half of the internet at once. Expect to see an issue reaching our servers, as well as a lot of other servers. Just because you can reach Google doesn't mean your internet isn't taking a beating

DNS Records page 404 on some servers
  • Resolved
    Resolved

    This incident has been resolved for now. We still have work to do but it's currently no longer your problem and that's the important part.

  • Identified
    Identified

    Mitigated on all but witcher.mxrouting.net server.

  • Investigating
    Investigating

    The DirectAdmin developers have pushed a change that breaks our DNS Records plugin page. These servers are currently seeing this:

    The most significant reason for the DNS Records page as of this moment is to find your Domain Verification key. As a temporary measure, please attempt to add new domains via Domain Setup in DirectAdmin, and you will be presented with a dialogue that provides you with a copy of your domain verification key.

    This workaround is not intended to be long term, this is considered a high severity event.

Inbound delay on glacier.mxrouting.net
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating

    We are currently experiencing a strange issue with Dovecot that is causing inbound mail delays on the glacier.mxrouting.net server. It has not been happening for long enough that anyone would likely have noticed, but we're putting up this status because it wasn't fixed in less than 60 seconds so we should get ahead of it.

Aug 2025 to Oct 2025

Next