Recovery and our view
Sage reported US Cloud and Desktop access issues on 11 November. Cloud recovery was confirmed on 13 November; on 20 November Sage released an automatic fix for version 2026.2 and remained in monitoring. Forum users described crashes and disputed security-update removal. Our advice: use the current vendor fix and test transactions; involve IT before changing security patches.
Provider record and timeline
- 12 November 2026 at 3:28 am · Pacific/Auckland
- 12 November 2026 at 4:13 am · Pacific/Chatham
- 12 November 2026 at 3:46 am · Pacific/Auckland
- 12 November 2026 at 4:31 am · Pacific/Chatham
- 14 November 2026 at 9:59 am · Pacific/Auckland
- 14 November 2026 at 10:44 am · Pacific/Chatham
- 21 November 2026 at 7:56 am · Pacific/Auckland
- 21 November 2026 at 8:41 am · Pacific/Chatham
Evidence and support
Keep error logs, request or submission IDs, affected users and UTC times. Open a case with your provider or reseller and ask which contract and deadline apply. These records do not establish an automatic credit, tax-deadline extension or compensation for lost revenue. Outside the affected market, check your actual service dependency.
Public discussion review
Public discussion is incomplete. No independently corroborated incident-specific customer discussion was retrieved for this article, except the Sage forum linked where relevant. Provider notices establish scope; forum anecdotes do not measure prevalence. Test recovery before clearing a backlog, retain an independent contact channel and reconcile queued work to avoid duplicates.