The N-able Mail Assure incident has left a sharp split between email delivery and administrative access. N-able says an investigation found unauthorized access to one server in its Mail Assure and SpamExperts Hosted Cloud environment. As of its 19 November 2026, 08:00 UTC update, mail flow and filtering were operating, while portal and API access remained disabled.
That split changes the operational decision. Teams can keep routing mail through the hosted filtering service, but they need temporary procedures for quarantined messages, configuration requests and workflows that depend on the portal or API. N-able lists affected services in the Americas, APAC and Europe for both products.
N-able Mail Assure Incident: Which Functions Work?
This matrix reflects N-able’s public status updates through 19 November at 08:00 UTC. “Unavailable” means the provider had not restored the function at that update, not that the underlying email messages were lost. Mail Assure and SpamExperts Hosted Cloud share the stated service pattern across the three listed regions.
| Function | Provider status at 08:00 UTC | Operational consequence |
|---|---|---|
| Core inbound and outbound mail flow | Available, according to N-able | Keep delivery checks in place; do not infer portal health from delivered mail. |
| Inbound and outbound filtering | Operating normally, according to N-able | Existing filtering continues, but changes may wait for management access. |
| Management portal and dashboard | Access disabled | Administrators may be unable to sign in or change settings. |
| API | Access disabled | Pause or queue automation that calls the hosted service. |
| Quarantine | Access offline pending validation | Users may be unable to view or release held messages. |
| Logging | Service offline pending validation | Investigations may have a temporary visibility gap in the hosted console. |
| Mailbox synchronization | Restoration and validation ongoing | Do not assume normal synchronization until N-able confirms it. |
N-able’s 18 November update says customers may be unable to view or release quarantined messages, review logs or change configurations, including domain additions and removals. Its 19 November update keeps quarantine, logging and mailbox synchronization within the restoration work. The status page does not give a restoration time for any of these functions. The outage also illustrates a provider dependency to track in a third-party risk management platform.
Why Did N-able Disable the Portal and API?
N-able first described the disruption as a platform configuration and service dependency problem. In its 18 November security update, the company revised that account after identifying unauthorized access to one server. It says it took steps to mitigate the threat and disabled UI and API access while investigation and remediation continue.
The company says each supporting service must pass security validation before it returns. Its 19 November updates describe controlled testing, platform hardening and continued investigation. Those statements explain the cautious restoration sequence; they do not identify the intrusion method, attacker or a software flaw requiring a customer patch.
N-able also says this event is unrelated to its separate N-central incident. Readers following the N-central security coverage should keep its product scope and response actions separate. The Mail Assure status page does not instruct customers to apply an N-central fix to the hosted mail service.
What Can Operators Do While Management Access Is Offline?
Use the provider’s stated split as the basis for a temporary operating mode. Verify mail arrival and filtering with ordinary delivery checks, while treating management workflows as unavailable. Record when a message cannot be released or a configuration change cannot be made, so the request can be revisited after restoration.
- Confirm deliveryCheck representative inbound and outbound mail through established routes; record time and result.
- Triage held mailLog quarantine review or release requests outside the portal and tell requesters access is delayed.
- Queue changesRecord requested domain and policy changes with an owner; do not assume an API call succeeded.
- Preserve contextKeep local mail-routing evidence and the timestamps of failed console or API attempts.
- Reconcile laterWhen N-able confirms restoration, review queued requests, logs and synchronization before closing them.
These are our continuity recommendations, not steps N-able says every customer must take. For an organization that relies on a provider for filtering, document who owns an urgent quarantine decision. Record what evidence can be collected locally and which provider update will trigger a return to normal operations.
N-able says it emailed partners with information relevant to their environments and whether action is required. If a partner did not receive that communication, N-able directs them to Technical Support. Use that direct channel for environment-specific direction rather than assuming the public status page covers every tenancy.
What Does the Disclosure Establish About Data Access?
N-able says its investigation had found no evidence of compromised customer data, including access to tenants’ mailboxes, at the time of its 18 November update. That is a dated statement about evidence then available. It does not establish that every possible access path has been excluded, and the investigation remains open.
Brandefense Blackhole counted 152 dark-chat posts matching the broad term “N-able” from 21 August to 19 November 2026. The measured unit is matching posts across that period, not incident reports, compromised mailboxes or verified data offers. This broad conversation count cannot connect a post to the Mail Assure event or resolve the company’s investigation.
Keep three questions separate in an incident response plan: whether hosted mail still flows, whether administrators can use supporting services and whether the provider confirms customer-data access. N-able has answered the first two for its 08:00 UTC update. Its statement on data describes current evidence, so monitor subsequent primary updates for a change in scope or restoration status.
Frequently Asked Questions
Is Mail Assure still filtering mail?
N-able said core mail flow and inbound and outbound filtering were operating normally at 08:00 UTC on 19 November 2026.
Can administrators release quarantined mail?
N-able said quarantine access remained offline during validation. Log urgent requests and check its status page or Technical Support for restoration updates.
Did N-able confirm tenant mailbox access?
N-able said on 18 November that its investigation had no evidence of customer-data compromise, including tenant mailbox access. Investigation was ongoing.
Is this the N-central incident?
No. N-able explicitly says the Mail Assure and SpamExperts Hosted Cloud incident is unrelated to the N-central incident.
