N-able Mail Assure Security Incident: Mail Flow Works While the Portal and API Stay Offline

N-able says a security incident affected the Mail Assure and SpamExperts Hosted Cloud environment and reports unauthorized access to one server there. Mail flow and filtering continue, but the management portal, API, quarantine, logging, and mailbox sync remain offline.

Reader ratingRate this article

Loading reader rating…

Privacy-conscious voting uses a signed random browser identifier and a short-lived network hash; the rating tables contain no raw IP-address column.

Reader ratings require JavaScript; the article remains fully readable without it.

ACTIVE SECURITY INCIDENT

Decision: N-able says a security incident affected its Mail Assure and SpamExperts Hosted Cloud environment, and reports unauthorized access to one server in that environment. Its investigation remains ongoing, and the company reports no evidence at the cutoff that customer data or tenant mailboxes were compromised.[1]

N-able says this incident is unrelated to the separate N-central incident.[1]

Reporting cutoff: November 19, 2026, 6:20 a.m. EST / 11:20 UTC.

Live statusMajor Outage, Identified, with no end time recorded at the cutoff.[1]
Affected service cohortMail Assure and SpamExperts Hosted Cloud in the Americas, APAC, and Europe.[1]
Mail handlingCore mail flow and filtering remain available and operating normally.[1]

What is working, and what is offline

Portal and API access remain disabled for now.[1]

Quarantine, logging, and mailbox synchronization remain offline while that work is ongoing.[1]

Until supporting services return, customers may be unable to sign in, view or release quarantined messages, review logs, or make configuration changes such as adding or removing domains.[1]

N-able says it emailed partners with environment-specific information and whether action is required or not; partners who did not receive that message are directed to N-able Technical Support.[1]

What remains unknown: The captured vendor record does not identify the attacker, initial-access method, dwell time, persistence scope, or an affected-account count. That source-level absence does not prove there was no broader impact.[1]

Practical guidance

  1. Confirm scope first. Check whether your provider actually uses Mail Assure or SpamExperts Hosted Cloud; email symptoms alone do not establish that this incident is the cause.[1]
  2. Do not bypass filtering. The vendor says filtering continues to operate normally, so loss of portal access is not evidence that filtering should be disabled.[1]
  3. Use the partner-specific notice. Follow the email sent for your environment and contact N-able Technical Support if it was not received.[1]

Source

  1. N-able incident 202672: Mail Assure and SpamExperts Hosted Cloud (public first-party JSON record; accessed November 19, 2026).