---
title: "Sage 50 U.S. partial outage"
description: "Availability issues affected cloud and desktop access, with desktop work continuing after cloud recovery"
incident_type: "Operational outage"
status: "active"
last_modified: "2026-11-17"
canonical_url: "https://www.ally.security/incidents/sage-50-us-partial-outage-2026"
markdown_url: "https://www.ally.security/incidents/sage-50-us-partial-outage-2026.md"
stix_url: "https://www.ally.security/incidents/sage-50-us-partial-outage-2026/stix.json"
---

# Sage 50 U.S. partial outage

Availability issues affected cloud and desktop access, with desktop work continuing after cloud recovery.

Last modified Nov 17, 2026 · 2 sources

## Summary

- **Environment:** Sage 50 U.S. cloud and desktop accounting applications
- **Operational impact:** Availability issues affected cloud and desktop access, with desktop work continuing after cloud recovery
- **Financial impact:** Financial impact remains unquantified in public reports

## What happened

On November 11, 2026, [Sage](https://www.sage.com/en-us/) reported that U.S. customers were unable to access both the cloud and desktop versions of Sage 50. Its [incident page](https://status.sage.com/incidents/kg9d2tz5390k) tracked recovery of the two versions separately. [1](#source-1)

## Impact

- Sage identified access problems in both applications. [1](#source-1)
- Sage reported the cloud version operating as expected on November 12. Desktop support work continued after that update. [1](#source-1)
- The desktop support note described crashes during ordinary accounting tasks after installing Windows updates. [2](#source-2)

## Timeline

### November 11, 2026 — Sage identifies access problems

Sage confirmed that U.S. users of the cloud and desktop applications were affected. [1](#source-1)

### November 12, 2026 — Sage begins monitoring the cloud service

Sage reported the cloud service was performing as expected. [1](#source-1)

### November 13, 2026 — Sage confirms cloud recovery

The November 13 update confirmed cloud recovery and said desktop repair work remained underway. [1](#source-1)

### November 17, 2026 — Briefing updated

This briefing was last reviewed and updated on November 17, 2026.

## Threat Group & Attack Vector

Sage’s [desktop support note](https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=261111142308050) attributed crashes to a November 10 Windows security update. [2](#source-2)

The cloud access issue’s cause remained unspecified in Sage’s incident updates. [1](#source-1)

## Response

Sage confirmed the cloud issue had been resolved and directed desktop users to its support article for a workaround while it continued work on a fix. [1](#source-1)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/sage-50-us-partial-outage-2026/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### Sage 50 (US) - Partial Outage

official · Sage · Nov 11, 2026

<https://status.sage.com/incidents/kg9d2tz5390k>

<a id="source-2"></a>

### Sage 50 crashing after installing Windows updates

official · Sage · Nov 11, 2026

<https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=261111142308050>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Resulted In · 100% confidence · current**  
   Sage 50 U.S. partial outage: On November 11, 2026, Sage reported that U.S. customers were unable to access both the cloud and desktop versions of Sage 50. Its incident page tracked recovery of the two versions separately.
2. **Resulted In · 100% confidence · current**  
   Sage 50 U.S. partial outage: Sage reported the cloud version operating as expected on November 12. Desktop support work continued after that update.
3. **Affected Organization · 100% confidence · current**  
   Sage 50 U.S. partial outage: Sage
4. **Resulted In · 100% confidence · current**  
   Sage 50 U.S. partial outage: The desktop support note described crashes during ordinary accounting tasks after installing Windows updates.
5. **Occurred At · 100% confidence · current**  
   Sage confirms cloud recovery: 2026-11-13T20:59:00Z
6. **Resulted In · 100% confidence · current**  
   Sage 50 U.S. partial outage: Sage identified access problems in both applications.
7. **Resulted In · 100% confidence · current**  
   Sage 50 U.S. partial outage: Sage confirmed the cloud issue had been resolved and directed desktop users to its support article for a workaround while it continued work on a fix.
8. **Resulted In · 100% confidence · current**  
   Sage 50 U.S. partial outage: The cloud access issue’s cause remained unspecified in Sage’s incident updates.
9. **Occurred At · 100% confidence · current**  
   Sage begins monitoring the cloud service: 2026-11-12T16:12:00Z
10. **Resulted In · 100% confidence · current**  
   Sage 50 U.S. partial outage: Sage’s desktop support note attributed crashes to a November 10 Windows security update.
11. **Occurred At · 100% confidence · current**  
   Sage identifies access problems: 2026-11-11T14:46:00Z

</details>
