Sage Outage History

Sage 50 customers in France experienced a 24-hour outage where bank transactions were not being received in their Sage 50 files, with users seeing "no bank transactions since your last login" error messages. The issue prevented customers from accessing their banking data within the application. The problem has been resolved and the service is now performing as expected.

Sage Intacct experienced a partial outage lasting 26.3 hours where some customers in Australia were unable to log in while others experienced performance slowness. The issue was identified and a fix was implemented, with the service returning to normal performance. The incident was resolved with ongoing monitoring to prevent recurrence.

Sage Intacct experienced a partial outage affecting the Project Contracts feature, where payments applied to Accounts Receivable invoices between May 9-12 caused data inconsistencies by unintentionally removing Project Contract line data and contract amounts. This resulted in missing or inaccurate contract totals and reduced visibility into Project Contract values for affected customers. The service was restored and monitored, with the issue fully resolved after 118.8 hours.

Sage experienced a partial outage affecting the Banking Service and Sage Intacct, where US customers were unable to connect multiple bank accounts simultaneously through multi-account linking functionality. A workaround was provided allowing customers to onboard each bank account separately, while other banking functions and Plaid/SISS connections remained unaffected. The issue was resolved after approximately 8 days with the service returning to normal performance.

Sage Operations experienced a major outage lasting 9.8 hours that prevented customers in Europe from accessing the service. The incident was identified and investigated by the service team, with monitoring implemented once service was restored. The issue was fully resolved and the service returned to normal performance.

Sage experienced a major outage affecting their AI Document Extraction service for 25.7 hours, preventing customers globally from using document extraction functionality. The outage impacted multiple Sage products including AutoEntry, Sage Intacct, and Sage Business Cloud Accounting across UKI, North America, and South Africa regions. The issue was identified and investigated over several hours before being resolved, with the service returning to normal performance.

Sage's banking service experienced a 104.9-hour partial outage affecting South African customers using FNB bank, who encountered re-authentication errors and severe slowness when onboarding new customers and syncing transactions. The issue impacted multiple Sage products including Sage Intacct, Banking Service, and Sage Business Cloud Accounting ZA, with customers receiving "authorization code not accepted" error messages. The third-party provider FNB applied a fix, though transaction delays persisted temporarily before full service restoration.

Sage Business Cloud Accounting ZA experienced a major service disruption lasting over 9 days, with customers encountering severe slowness, "can't reach this page" errors, and complete service unavailability during multiple emergency maintenance windows. The service was intermittently restored with degraded performance and disabled third-party integrations before being fully resolved. Multiple scheduled and emergency maintenance sessions were required to address the underlying issues and restore normal operations.

Sage Active experienced a partial outage affecting the iOS mobile application for customers in France, Spain, and Germany, preventing access to the app for approximately 29 hours. The web version and other platforms continued to function normally during this period. The issue was resolved and the service returned to expected performance levels.

Sage People experienced a partial outage lasting approximately 76 hours where a subset of UK customers were unable to transfer Payflow files to vendor SFTP endpoints. All other product functionality remained operational during the incident. The issue was resolved and the service returned to normal performance.