Sage Outage History

Sage Online (FR) and Sage 100 Partner Cloud (FR) experienced a keyboard input issue where the SHIFT key stopped functioning for French customers, preventing them from entering certain characters and symbols. The incident lasted 67.2 hours, during which users could work around the problem by using CAPS LOCK for some characters or copy-pasting from other sources. The issue was resolved through a scheduled 2-hour maintenance window on April 22nd between 20:00-22:00 CET.

Sage's Brightpearl service experienced degraded performance for 3.3 hours, affecting the platform's functionality. The team investigated the issue and implemented monitoring measures to prevent reoccurrence. The service was fully restored and returned to normal performance levels.

Sage's E-Invoicing service experienced an intermittent issue where customers in France encountered validation errors when sending invoices. The problem affected the E-Invoicing component for 76.1 hours while Sage investigated and worked to resolve the underlying cause. The issue has been resolved and the service is now performing as expected with continued monitoring to prevent reoccurrence.

Sage Intacct experienced a partial outage affecting Banking services for a subset of UK customers using specific banks including NatWest, UniCredit, Bank GmbH, HSBC, and Metro Bank, preventing them from downloading transactions. The issue lasted approximately 6.9 hours before being fully resolved. Service is now available and performing as expected.

Sage experienced a banking service outage that prevented South African customers from onboarding and re-authenticating their FNB bank feed connections, with users receiving authorization code rejection errors. The issue affected the Banking Service and Sage Business Cloud Accounting ZA components. The incident lasted approximately 117.6 hours before being resolved on April 21st, with the service returning to normal performance.

Sage experienced a partial outage affecting the Banking Service and Sage Intacct components for 14 minutes. The cause of the issue was identified and a fix was implemented. The incident was classified as minor and has been resolved.

Sage's AutoEntry service experienced degraded performance for 19.5 hours, with customers globally reporting slowness when using the platform. The issue was identified and a fix was implemented, with the service restored to normal performance levels. The incident has been resolved and AutoEntry is now operating as expected.

Sage.com websites experienced a major global outage lasting 40 hours from April 14-16, 2026. The company identified that their websites were completely down worldwide and worked to investigate and resolve the issue. The service was restored and returned to normal performance, with ongoing monitoring implemented to prevent recurrence.

Sage's Banking Service experienced a partial outage that prevented customers in South Africa from syncing new transactions and onboarding accounts with Standard Bank through the Yodlee connection. The issue specifically affected current, savings, credit, and investment account connections, requiring customers to either switch to an alternative Standard Bank connection or manually import bank files as a workaround. The service was fully restored after 172.3 hours with all functionality performing as expected.

Sage Intacct customers globally experienced a 63.4-hour outage preventing them from establishing bank connections through AccessPay. The banking service was completely unavailable during this period, affecting financial operations and connectivity. The issue was identified, a fix was implemented, and service was restored with ongoing monitoring to prevent recurrence.