P.K. SHARMA

Cyber security intelligence, AI governance, practitioner analysis

N-able's status page blamed configuration, then 13 h 31 min later said unauthorized access hit a Mail Assure server

N-able's Uptime page gave platform configuration and service dependencies as the cause at 13:33 UTC on 17 November, then at 03:05 UTC on 18 November said unauthorized access to one of its servers. Read on 20 November 2026: the portal and API were still offline.

By · LinkedIn · · 19 min read

N-able's page named configuration, then 13 h 31 min 27 s later named unauthorized access

N-able's Uptime page for event 202672 printed a cause at 13:33:42 UTC on Tuesday 17 November 2026: it was "a combination of platform configuration and service dependencies". At 03:05:09 UTC on Wednesday 18 November the same page said N-able had "determined that the disruption was caused by a security incident" and that it was "aware of unauthorized access to one of the servers" in the Mail Assure and SpamExperts Hosted Cloud. Between the two statements are 13 h 31 min 27 s (derived: 13:33:42 to 03:05:09 across midnight), and the page printed no entry in that window. The event's start stamp is 03:00:00 UTC on 17 November. At the latest entry this site saved, 11:59:59 UTC on 20 November, the page was 3 d 8 h 59 min 59 s past that start stamp (derived) and still said that "The portal and API remain offline".

That is the checkable fact. The page is N-able's own and it corrects itself in plain words: "we believed we had remediated the issue". This brief reports what the page prints, in the order it printed it, and then what it leaves out. N-able is the victim here and its only public statement is this page, so the aim is to read it closely, not to second guess it. Here is what the saved pages do not establish:

  • When the unauthorized access began or ended. Not stated. The 17 November 03:00:00 UTC stamp is the status page's start stamp, not a date of access.
  • When or how N-able found it. Not stated. The page prints no discovery date.
  • Which server, or how the access was gained. Not stated: no entry route, no flaw, no CVE id, no indicator.
  • How many customers or partners are affected. Not stated.
  • Whether any data left. N-able says it has no evidence that customer data was compromised, at that point in an investigation it calls ongoing. That is an absence of evidence at a time, not a finding.
  • Who did it. Not stated. The page names no actor and does not use the word breach or the word attackers; BleepingComputer, a secondary, uses both.
  • Why the first statement of cause named configuration. Not stated.
  • When the portal and API come back. Not stated.

What the page printed, in the order it printed it

Diagram 1 draws the page's stamps on one time axis, in hours, from 16 to 21 November. The 16 November notice has no hour and is drawn as a dashed day band. The page prints sixteen entries in all (derived: counted on the saved copy). The first, at the start stamp, carries a status word and no text. The next three, on 17 November, say that N-able is still looking: "continuing to investigate the root cause" at 06:10:45 and again at 10:22:45, with "Dashboard access is affected." added at 06:10:45.

Drawn from N-able's Uptime page for event 202672 as saved at 15:13 UTC on 20 November 2026. Positions come from one time scale; intervals are derived. The page prints every stamp in UTC.

At 13:33:42 UTC the page said N-able "has identified the root cause of the issue, and a fix is still being developed", that "Remediation required rebuilding affected infrastructure and updating several platform components", and that "Core mail flow has remained available". Then there is nothing for 13 h 31 min 27 s (derived). The next entry, at 03:05:09 UTC on 18 November, is the longest on the page and the one that changes the cause. After it the page settles into a pattern: an update at intervals of roughly 3 h 43 min to 8 h 39 min (derived), each saying that testing, validation and hardening continue, that mail flow and filtering work, and that the portal and API stay disabled.

The table lists every entry as the saved copy prints it. The what it says column is this site's short wording except where it is in quotation marks.

Table 1. The sixteen entries on N-able's Uptime page for event 202672, as saved at 15:13 UTC on 20 November 2026, oldest first. All stamps UTC.

Stamp (UTC)Status wordWhat the entry says
17 Nov 03:00:00InvestigatingNo text printed. This is the start stamp in the page header.
17 Nov 06:10:45Update"continuing to investigate the root cause". "Dashboard access is affected." "Mail Filtering remains operational."
17 Nov 10:22:45Investigating"continuing to investigate the root cause". No mail statement.
17 Nov 13:33:42IdentifiedRoot cause "a combination of platform configuration and service dependencies"; fix still being developed; "Core mail flow has remained available"; portal, quarantine, logging and mailbox synchronization "undergoing restoration and validation".
18 Nov 03:05:09IdentifiedTitled "Mail Assure and SpamExperts Hosted Cloud Security Incident". Unauthorized access to one of the servers; says it does not have evidence of customer data compromise; unrelated to the N-central incident; UI and API access "proactively disabled"; email flow and spam filtering unaffected.
18 Nov 11:44:01IdentifiedRestoring and validating the portal, quarantine, logging and mailbox synchronization; lists what customers may be unable to do.
18 Nov 20:18:08IdentifiedPortal (UI), APIs, quarantine and logging "remain offline"; partners contacted directly by email; contact N-able Technical Support if not received.
19 Nov 00:01:02UpdateRemediation measures in testing; each service must pass security validation in a controlled environment before coming back; portal and API stay disabled.
19 Nov 04:01:10UpdateTesting and more security hardening; investigation continuing; portal and API still disabled "as a precaution".
19 Nov 08:00:01UpdateValidating and hardening the portal and supporting services (quarantine, logging, mailbox synchronization); services stay offline.
19 Nov 15:16:52IdentifiedRestoration continued overnight; each service restored in a controlled way once it passes security validation.
19 Nov 19:55:55UpdateRemediation testing and further hardening; investigation continuing.
20 Nov 00:00:37UpdateSays being unable to reach the portal, quarantine and logs "affects your day-to-day operations"; restoring safe access is the top priority.
20 Nov 04:00:24UpdateRestoration work around the clock; services return once they meet security requirements.
20 Nov 08:06:56UpdateRemediation progressed through the night; completed measures under test; portal and API "still disabled as a precaution".
20 Nov 11:59:59Identified"our investigation into the incident is ongoing"; each component must pass security validation; "The portal and API remain offline".

Counting the saved copy, fourteen of the sixteen entries carry a statement that mail flow, mail delivery or filtering works (derived). The two that do not are the empty start entry and the 10:22:45 entry on 17 November. The page header at the top of the saved copy says "Mail flow and filtering continue to operate; dashboard, API and quarantine access remain offline while we restore services safely."

Configuration, then a security incident: what each entry says the cause is

Diagram 2 puts every cause statement on the page side by side. Both statements that matter are N-able's own. The 17 November entry says the issue "was traced to a combination of platform configuration and service dependencies within the Mail Assure & Spam Experts Hosted Cloud environment". The 18 November entry says "Our earlier update said the disruption came from platform configuration and service dependencies and we believed we had remediated the issue", then "As we continued our investigation, we determined that the disruption was caused by a security incident".

Drawn from N-able's Uptime page as saved at 15:13 UTC on 20 November 2026. Cause words are copied as printed; the count of three of nine is derived.

Two details are worth setting beside each other, and nothing here is resolved. First, the 13:33:42 entry says "a fix is still being developed" and that "Remediation required rebuilding affected infrastructure and updating several platform components". The 03:05:09 entry says N-able "believed we had remediated the issue". The page does not say when that belief formed or when it ended, and it printed nothing in the 13 h 31 min 27 s between the two entries (derived). Second, the 18 November entry says N-able has "taken steps to mitigate the threat and are continuing to harden our services to reduce the risk of recurrence". Mitigating a threat is a different word from containing it, and the page does not use the word contained or the word contain anywhere.

The wording also carries two label questions. The event title as saved starts with the words Security Incident, and the page summary says "N-able is responding to a security incident affecting Mail Assure and SpamExperts Hosted Cloud." Whether the event carried that title before 03:05:09 UTC on 18 November is not on the saved copy. And the severity in the header is "Major Outage", next to a body that says mail delivery is "fully operational". Both are N-able's words about different things, and the next section sets them apart.

The five dates, kept apart

An incident page mixes several dates under one heading, and the saved copy answers some and leaves others blank. Table 2 separates them.

Table 2. The access window, discovery, containment, notification and publication dates, as N-able's Uptime page and BleepingComputer print them. Read 20 November 2026.

DateWhat the saved pages stateNot stated
Access windowNothing. N-able says it is "aware of unauthorized access to one of the servers".When the access began, when it ended, how long it lasted
DiscoveryNothing as a date. The 03:05:09 UTC entry on 18 November says the investigation "determined" a security incident.When the access was found, by whom, and how it was found
ContainmentN-able says it has "taken steps to mitigate the threat" and "proactively disabled UI and API access". The 06:10:45 UTC entry on 17 November already says "Dashboard access is affected".Whether the access is closed; what the steps were; the date any step finished
NotificationCustomers were told of "a service disruption" on 16 November (N-able, in the 18 November entry). Partners were contacted "directly by email" with information "relevant to their environment" (20:18:08 UTC, 18 November).The hour of the 16 November notice; whether any customer notice named a security incident; how many partners received an email; what the email said
PublicationThe security incident statement is stamped 03:05:09 UTC on 18 November. BleepingComputer prints "November 20, 2026" and "08:18 AM", no zone.Whether the page title and summary were changed on 18 November

One of these dates sits oddly against the page's own header. N-able says it informed customers about a service disruption on November 16, and the page's start stamp is 03:00:00 UTC on 17 November. If 16 November is read in UTC it ends three hours before the start stamp (derived: 24:00 to 03:00). The saved copy gives no zone for 16 November, so this site cannot put the notice and the start stamp in order. What can be said is that the page's record begins after N-able says its customers were first told.

BleepingComputer, a secondary, says N-able "initially blamed" the outage on the configuration wording "On Tuesday", and that "one day later" N-able disabled UI and API access and confirmed unauthorized access. The page agrees with Tuesday for the configuration statement (17 November, 13:33:42 UTC). It puts the security incident statement on Wednesday 18 November: 13 h 31 min 27 s after the configuration statement, and 24 h 5 min 9 s after the start stamp (derived). Both are close to one day, which is what BleepingComputer says. What the page does not say is that UI and API access were disabled only on the Wednesday: its 17 November entries already say the dashboard was affected (the next section).

What is offline, what is not, and why the two statements do not conflict

Almost every status update says that mail still flows (14 of the 16 entries, derived). The 20 November 11:59:59 UTC entry says "Mail delivery and filtering remain fully operational." The 18 November 03:05:09 UTC entry says "Email flow and spam filtering in both Mail Assure and SpamExperts Hosted Cloud continue to operate unaffected." At the same time the header says Severity: Major Outage and the entries say the portal, API, quarantine and logging are offline. Diagram 3 sets each entry's statements side by side, so that the two scopes are visible.

Drawn from N-able's Uptime page as saved at 15:13 UTC on 20 November 2026. Red is offline, disabled or affected; amber is restoration under way; green is stated as working; dashed means the entry does not name that part.

Read together, the page says two different things about two different sets of parts, and both can be true at once. Mail delivery and filtering are the gateway's job: inbound and outbound mail passes through. The portal, API, quarantine, logging and mailbox synchronization are how a partner sees, releases and changes things. The 18 November 11:44:01 UTC entry spells out the second set: "customers may be unable to sign in to the control panel, view or release quarantined messages, review logs, or make configuration changes such as adding or removing domains".

Where the page goes quiet is what happens to a message that the filter quarantined while the quarantine was offline. The entries do not say whether quarantined messages and logs are being kept, whether they are accessible to N-able, or whether any were in scope of the unauthorized access. The 20 November 00:00:37 UTC entry says only that being unable to reach the portal, quarantine and logs "affects your day-to-day operations".

Two more differences sit inside the page. The 17 November 13:33:42 UTC entry already says the management portal, quarantine, logging and mailbox synchronization "have been undergoing restoration and validation", while the 18 November entry says N-able "proactively disabled UI and API access". The 17 November 06:10:45 UTC entry said "Dashboard access is affected." From that first mention to the proactive disabling statement is 20 h 54 min 24 s (derived). The page does not say whether the dashboard was affected by the cause or by the response, or when the UI and API were switched off. And the 18 November 20:18:08 UTC entry lists the portal, APIs, quarantine and logging as offline and does not name mailbox synchronization, which the entries before and after it do.

What N-able says about the other incident, and what a secondary adds

The 18 November entry says "This is unrelated to the N-central incident." That is a statement by N-able in one sentence; the page gives no reason and no evidence. BleepingComputer repeats it and adds its own description of the other incident: "an N-central incident that forced it to take all hosted N-central environments offline to patch more than 30 zero-day flaws". That description is the secondary's, and this brief does not rely on it. This site has earlier briefs on the N-central incident; it does not link them here because their live pages were not re-read for this brief.

BleepingComputer's own headline and opening use words the page does not: "recent security breach", "attackers who breached one of its servers". N-able's wording is "unauthorized access to one of the servers", with no actor and no mention of a breach. BleepingComputer also says that "After detecting the attack, N-able also alerted customers via email". The page says customers were told of a service disruption on 16 November, before it called the cause a security incident, and that partners were emailed on 18 November (20:18:08 UTC). The secondary's order of events is not the page's order.

Where the pages differ, with nothing resolved

Table 3. Differences between and inside the saved pages. Each is reported as printed; none is resolved.

PointOne page printsAnother prints
When the outage was first called a security matterBleepingComputer: N-able "initially blamed" configuration "On Tuesday" and "one day later" confirmed unauthorized accessPage: configuration statement 17 Nov 13:33:42 UTC (Tuesday); security incident statement 18 Nov 03:05:09 UTC (Wednesday); 13 h 31 min 27 s apart (derived)
When UI and API access went offlinePage, 18 Nov 03:05:09: "We have proactively disabled UI and API access"Page, 17 Nov 06:10:45: "Dashboard access is affected." Page, 17 Nov 13:33:42: portal "undergoing restoration and validation"
What is known about customer dataN-able: "at this time we do not have evidence that customer data was compromised, including access to tenants' mailboxes"The same entry: "The investigation is ongoing". 20 Nov 11:59:59: "our investigation into the incident is ongoing"
Whether service is up14 of 16 entries (derived): mail flow and filtering operateHeader: Severity "Major Outage". Entries: portal, API, quarantine and logging offline
Whether the problem was fixed17 Nov 13:33:42: "a fix is still being developed"; "Remediation required rebuilding affected infrastructure"18 Nov 03:05:09: "we believed we had remediated the issue"
When customers were toldN-able, 18 Nov entry: "On November 16, we informed customers about a service disruption"Page start stamp: 17 Nov 03:00:00 UTC. BleepingComputer: "After detecting the attack, N-able also alerted customers via email"
Words for what happenedN-able: "unauthorized access to one of the servers"; "security incident"BleepingComputer: "breach", "attackers", "cyberattack"
What N-able took downBleepingComputer: N-able "took down the management portal (dashboard), as well as quarantine, logging, and mailbox synchronization"Page, 18 Nov 03:05:09: UI and API access "disabled"; quarantine, logging and mailbox synchronization described as under restoration or "offline"

The first row is a difference in framing, not in fact. BleepingComputer's phrase "one day later" fits both anchors the page offers: the start stamp is 24 h 5 min 9 s before the security incident statement and the configuration statement is 13 h 31 min 27 s before it (derived). This site does not choose between them.

What N-able states, and what it does not

Table 4. What the saved pages establish and what they leave open. Read 20 November 2026.

QuestionStatedNot stated
What happened?Unauthorized access to one of the servers in the Mail Assure and SpamExperts Hosted Cloud (N-able, 18 Nov 03:05:09 UTC)Which server; how access was gained; how long it lasted
Was mail affected?Mail delivery and filtering "remain fully operational" (20 Nov 11:59:59 UTC)Whether any mail was delayed, lost or read
Was customer data taken?"we do not have evidence that customer data was compromised, including access to tenants' mailboxes", at that timeWhat was looked at; whether quarantine content or logs were in scope; whether the statement has changed since 18 Nov
Who is affected?Six services in three regions are listed as impacted; partners were emailed (18 Nov 20:18:08 UTC)A count of customers or partners; which of them were told what
What is offline?Portal and API remain offline; quarantine and logging offline (18 Nov 20:18:08 UTC); header: dashboard, API and quarantineWhen any of them returns; what validation each must pass
Who did it?NothingAn actor, a motive, a technique, a CVE or a flaw in N-able code
Is it linked to N-central?N-able: "unrelated to the N-central incident"The basis for that statement
Why did the first statement name configuration?NothingWhether it was an honest early reading or an incomplete one

What the product is, as far as the saved pages say

N-able sells Mail Assure and SpamExperts Hosted Cloud and wrote the only primary statement on this incident, so its interest is to reassure customers and keep the service running; that is stated once here and applies to every quotation above. The saved pages do not define the products. They describe them through what they do: "inbound and outbound mail filtering", a management portal, a control panel, "quarantined messages", logs, domains added or removed, "mailbox synchronization", partners and tenants. The page does not say whether partners are resellers or managed service providers; this site does not assume it. What a reader can take from the page is that these are a filter in the mail path and a management plane around it, and that on 20 November the plane was offline while the path ran.

The saved pages print no indicators of compromise, no CVE id, no entry route and no configuration to check. The one list the page prints is the services impacted, copied exactly below.

Text
Mail Assure (Americas)
Mail Assure (APAC)
Mail Assure (Europe)
SpamExperts (Americas)
SpamExperts (APAC)
SpamExperts (Europe)
N-able Uptime page, event 202672, the services impacted list as printed, in the copy saved at 15:13 UTC on 20 November 2026.

What to do, in order

N-able's own instruction comes first and is short: partners were contacted "directly by email with information relevant to their environment and whether action is required or not", and "If you have not received this communication, please contact N-able Technical Support." The rest of this list is this site's suggestion, not N-able's advice.

Take this with you

Checklist (N-able's instruction first, then this site's suggestions)

  • N-able: check for the partner email for your environment; if you did not receive it, contact N-able Technical Support.
  • If you resell or run Mail Assure or SpamExperts, read that email in full and record which of your tenants it covers (this site's suggestion).
  • Do not read mail flow as safety. The page says mail and filtering run, and also that the portal, API, quarantine and logs are offline; those are different parts (this site's suggestion).
  • Ask N-able in writing whether quarantine content and logs for your tenants were in scope of the unauthorized access, and keep the reply (this site's suggestion).
  • Plan for an email security outage that lasts days: decide where quarantine release, domain changes and log review will come from while the portal is offline (this site's suggestion).
  • Treat a status page statement of cause as provisional until the incident closes. This page changed its own cause once (this site's suggestion).
  • When access returns, rotate any credentials or API keys you stored in the portal or in integrations that call the API, and review who has access (this site's suggestion).

The question the page leaves open

N-able's page changed its cause once in 13 h 31 min 27 s, and says at 20 November 11:59:59 UTC that the investigation is still going. If a statement of cause can be replaced within a day, which of today's statements, "we do not have evidence that customer data was compromised" among them, is the one N-able will still stand behind when the portal comes back, and where will it say so?

Key facts

Sources

  1. PrimaryN-able Uptime status page, event 202672, Security Incident for Mail Assure and SpamExperts Hosted Cloud, all regions: header, services impacted and the sixteen timeline entries, 17 to 20 November 2026. A living page, rendered text saved at 15:13 UTC on 20 November 2026; the newest entry read is stamped 11:59:59 UTCN-ableaccessed 2026-11-20
  2. Reported bySecondary report of 20 November 2026 on the N-able outage: used to compare its wording, its Tuesday and one day later framing and its account of customer notice with the status page. Attributed where quotedBleepingComputeraccessed 2026-11-20

Share this briefing

Know someone who owns this problem? Send it to them.

Related briefings

The briefing, in your inbox

Practitioner analysis of cyber and AI security news. No vendor noise.

How often

Every new briefing in one email, at 7am, or at 7am, 12:30pm and 6pm. Nothing is sent when nothing is new. Unsubscribe any time.