Support
System Status
This page explains how we handle and communicate service incidents, and records the recent ones. It is not an automatic status dashboard, and the absence of a notice here does not mean everything is fine right now — a page that claims all-clear is worse than no page at all on the one day it isn’t.
Recent incidents
·Resolved
Microsoft 365 outage delayed mail to Microsoft 365 mailboxes
- Impact
- Resolved. Mail held during the outage was delivered, and bounced mail was recovered.
- Affects
- Microsoft 365, Outlook, and Exchange Online mailboxes only. Every other mail platform delivered normally.
Microsoft’s Exchange Online outage, which it tracked as EX1550543 with a related advisory, MO1550821, began at about 8:20 AM Pacific on November 12 (16:20 UTC). Users could not connect to their Microsoft 365 mailboxes through several connection methods, first in the Americas and then in other regions.
Microsoft traced it to a process on its servers that sets up secure connections: the process became overwhelmed, and the servers stopped processing requests. Service came back region by region through November 13, and Microsoft has since marked the incident resolved. It said it found no evidence of malicious activity and will publish a full Post-Incident Report in its advisory.
From about 10:40 AM Pacific on November 12 (18:40 UTC), Microsoft’s mail servers turned away much of the mail we delivered to them with temporary errors. We held every message and kept retrying, which every plan does for up to 15 days, including Basics. From about 4:45 AM Pacific on November 13 (12:45 UTC), Microsoft accepted mail normally again, and the mail we held was relayed to Microsoft’s servers. Filtering worked normally throughout, and mail to every other platform was delivered as usual.
For some customers whose Microsoft 365 connector accepts mail only from MailRoute, Microsoft wrongly refused messages permanently during the outage, so their senders received bounce notices. We keep a copy of every message we deliver for seven days, so we recovered those messages, re-delivered them on November 13, and wrote to each affected customer with the details.
If mail to your Microsoft 365 users arrived late on November 12 or 13, or arrived in a burst, that is what you were seeing. Nothing needs to be resent. Re-delivered messages keep their original date and carry the header X-MailRoute-Replay.
This incident is closed. Microsoft’s advisories, linked below, will carry its Post-Incident Report.
- Microsoft 365 Service health: EX1550543 →Microsoft’s own advisory. Readable by Microsoft 365 administrators signed in to your tenant; there is no public version of this page.
- Microsoft 365 Service health: MO1550821 →Microsoft’s related advisory. Also readable only by Microsoft 365 administrators signed in to your tenant.
·Resolved
MailRoute Hosted Mail migration complete
- Impact
- Every mailbox moved with its mail intact. Some desktop apps may still be re-downloading.
- Affects
- MailRoute Hosted Mail mailboxes only. Filtering and delivery to other mail platforms were not affected.
We have moved every MailRoute Hosted Mail mailbox to new servers. The work ran on Sunday, October 4, from about 2:00 p.m. to 6:00 p.m. Pacific, one mailbox at a time.
Your mail is safe. Every mailbox was copied to the new servers before it switched over, and each switch was checked folder by folder against the original. Incoming mail was delivered normally throughout.
Nothing changes in how you connect: same server names, same password, no settings changes. Your folders, messages, read and flagged status, and server-side filters, including vacation replies, came with your mailbox.
Mail apps that keep a full copy of every message on your computer, such as Apple Mail on the Mac (its default setting) and Outlook in Cached Exchange Mode, are downloading all of your mail again. Nothing is wrong and nothing is lost: the app is rebuilding its local copy. For a large mailbox this can take a few hours, and some apps show newly arrived mail only once the download finishes. In the meantime, webmail and phone mail apps show your complete mailbox, including new mail, right away.
If you use POP and leave mail on the server, older messages may have been downloaded again as new. If a phone or mail app shows an error, closing and reopening it, or re-entering the same password, fixes it. If anything still looks wrong, contact support and we will check your mailbox.
·Resolved
Planned upgrade of Email Continuity
- Impact
- Complete. Delivery and filtering were not affected.
- Affects
- Email Continuity (continuity.mailroute.net) only. Normal delivery and filtering were not affected.
On Sunday, October 4, we moved Email Continuity to new servers. The work is complete.
Email delivery and filtering continued as normal throughout. Copies bound for Email Continuity during the move were held on our filtering servers and have been delivered to the new servers. Nothing was lost.
Email Continuity is at the same address, continuity.mailroute.net, with the same sign-in. If you were signed in when we switched over, sign in again. Personal settings in the Email Continuity webmail, such as a signature or saved contacts, need to be set up again.
·Resolved
Microsoft rate limiting delayed mail to Microsoft 365 mailboxes
- Impact
- Delivery delayed about six hours. No mail lost, rejected, or bounced.
- Affects
- Microsoft 365, Outlook, and Exchange Online mailboxes only. Every other mail platform delivered normally.
From about midnight Pacific (07:00 UTC) until mid-morning, Microsoft rate-limited inbound mail across its Exchange Online infrastructure, returning 451 4.7.500 Server busy to sending systems worldwide. Mail to Microsoft-hosted mailboxes was delayed. Every other platform delivered normally throughout.
Microsoft tracked it as EX1467029, an Exchange Online service degradation, and dated the start to 3:19 AM Pacific — we saw the deferrals about three hours earlier. Independent providers across North America and Europe reported the identical error from unrelated networks. No MailRoute system was blocked or blocklisted.
In its 4:59 AM Pacific update Microsoft identified the enforcement of a specific anti-spam model as contributing, added the affected sending addresses to an allow list as a first mitigation, and worked to disable the model. We saw that land from about 5:57 AM Pacific, when deliveries began going through and the queues started draining.
As of 6:42 AM Pacific every queued message has been delivered, and delivery to Microsoft-hosted mailboxes is back to normal. No mail was lost, rejected, or bounced at any point: messages were held in our queues and retried, which every plan does for up to 15 days, including Basics.
If mail to your Microsoft 365 users arrived late this morning, or arrived in a burst, that is what you were seeing. Nothing needs to be resent. Delay notifications your senders received from their own mail systems were informational, and those messages have been delivered.
We released the backlog in stages rather than all at once, per Microsoft’s requirements. Filtering, quarantine, and the control panel were unaffected throughout.
Email Continuity — on Enterprise plans, and on legacy accounts with the add-on — held a readable copy of the delayed mail at continuity.mailroute.net while the queues drained.
We are closing this out: delivery has been normal since 6:42 AM Pacific. Microsoft’s own advisory, linked below, carries their final word on the incident.
- Microsoft 365 Service health: EX1467029 →Microsoft’s own advisory. Readable by Microsoft 365 administrators signed in to your tenant; there is no public version of this page.
·Resolved
Inbound mail delays through one datacenter
Starting at 6:43 AM Pacific (13:43 UTC), mail moving through one of our datacenters was delayed by up to about an hour. Two fiber cuts in the network of Cogent, an upstream transit provider, caused increased latency and intermittent disruption across Los Angeles and the southwestern United States. Traffic through our other datacenters was not affected.
No mail was lost. Delayed messages held in our queues and delivered normally once routing settled, about 60 to 70 minutes after the delays began. If mail arrived late on the morning of September 2 and then caught up, that is what you were seeing. Nothing needs to be resent.
Cogent repaired the fiber and closed the event at 2:11 AM Pacific on September 3 (09:11 UTC), a little over 19 hours after it began. Routing inside our own network is back to normal, and we are closing this out. Cogent tracked the event as master case NA306633403; it has since cleared the event from its public network status page.
If something looks wrong right now
Email us at support@mailroute.net or call (888) 485-7726. A real person reads support mail, including outside business hours. You do not need to diagnose the problem before you contact us, and you will not be asked to work through a phone tree.
What happens to your mail during an incident
Inbound mail queues. Every plan holds inbound messages and retries delivery for up to 15 days if your mail server stops responding, so nothing bounces while the problem is being sorted out.
Enterprise plans add a rolling 30-day store of clean mail that is always on, not spun up in response to an outage. Your team can log in and keep reading and sending while the underlying server is unavailable, with no gap where the most recent messages are missing.
Telling our problem from yours
Most reports that reach us as “MailRoute is down” turn out to be a mail server, a DNS change, or a firewall rule on the customer side. The fastest way to tell the difference is the mail log in your admin portal: it shows what we received, what we did with it, and what your server said when we tried to deliver it.
If the log shows mail arriving and queueing, we have your mail and the delivery target is the thing to look at. If it shows nothing arriving at all, check your MX records first, then contact us.
How we communicate about incidents
For confirmed service-affecting incidents we contact affected domain administrators directly by email. We do not wait for customers to notice and ask.
Planned maintenance that could affect mail flow is announced in advance to administrators of the affected domains. Routine work that does not affect delivery is not announced, because filling your inbox with notices you do not need is its own kind of noise.
Occasionally work cannot wait — a security fix, or hardware that will fail worse if we leave it running. We give as much notice as the situation allows, sometimes only while the work is already underway, and we post what we did and why we could not give the usual notice within five business days.
Announced maintenance windows, and emergency work of that kind, are excluded from the availability commitment in our Service Level Agreement, which covers inbound mail acceptance at 99.999% and carries a service credit if we miss it. An outage we did not choose is not maintenance, and is not excluded.
Subscribe to status updates
Every incident on this page is published to an Atom feed at /status/feed.xml. Entries carry the same text you see here, and an entry is revised in place as an incident moves from monitoring to resolved, so a reader will re-surface it when the state changes. This is in addition to the direct email above, not instead of it — it is there for the people who are not the domain administrator on record, which usually means a helpdesk or a partner watching several customers at once.
To route it into Slack, paste this into whichever channel should receive it:
/feed subscribe https://mailroute.net/status/feed.xmlSlack reads the feed with its built-in RSS app, so nothing needs installing on either side. For Microsoft Teams, Discord, a feed reader, or your inbox, see subscribing to status updates.
Support hours
Monday – Friday, 7:30 AM – 4:30 PM Pacific. Emergency support is available 24/7 by email for every customer. Enterprise plans add phone support; after-hours help is always email-first.
A live status dashboard backed by real monitoring is planned. Until it exists, this page tells you how to reach us and what your mail is doing rather than guessing on your behalf.
Something not behaving the way it should?
Tell us what you're seeing. You do not need to diagnose it first.