Sage Outage History

Sage Expense Management experienced a partial outage where customers globally were unable to access three key websites (cards.fylehq.com, careers.fylehq.com, and help.fylehq.com), with users being redirected to maintenance pages or error messages. The access to help.fylehq.com was restored first, followed by the resolution of the remaining two URLs. The incident lasted 1.9 hours and was fully resolved with all services returning to normal performance.

Sage DPW Cloud experienced a 3.5-hour partial outage that prevented customers in Austria from opening PDF documents, displaying error messages when attempting to access them. The issue affected the Sage DPW Cloud service, though customers could work around the problem by downloading PDFs to open them separately. The root cause was identified and resolved, with service returning to normal performance.

UK customers experienced connection errors when trying to access the HMRC secure mailbox through Sage 50 Payroll, receiving "It has not been possible to establish a connection to your HMRC Mailbox" messages. The issue affected Sage 50 Payroll's integration with HMRC services for approximately 50 days. The incident was resolved by directing customers to follow specific instructions provided through Sage's knowledge base, with users advised to contact HMRC's Online Services Helpdesk for additional support during the outage period.

Sage Business Cloud Self Service experienced a major outage lasting 7.5 hours that prevented customers in South Africa from logging in, with users encountering an "error posting to API" message despite the landing page loading successfully. The technical team identified the root cause and deployed a fix to the production environment. The service was fully restored and returned to normal performance.

Sage Intacct experienced a partial outage affecting a subset of customers in the USA who encountered an "Unexpected processing error" when trying to access the Lists beta interface functionality. Other product features remained operational during the incident. The issue was resolved after 58 minutes with full service restoration.

Sage Intacct experienced a partial outage lasting 1.6 hours where customers could not make changes to transaction definitions in Purchasing due to a global issue. Users encountered an error message stating "You cannot change the primary document workflow setting because documents already exist for this transaction definition" while all other product functionality remained operational. The issue was identified and resolved, with the service returning to normal performance.

An issue prevented a subset of customers from accessing Sage Intacct Planning through SSO for approximately 1 hour. The problem has been resolved and the service is now performing as expected, with ongoing monitoring to prevent reoccurrence.

Sage's Brightpearl service experienced an intermittent global issue lasting 43.3 hours that caused WMS customers to encounter "whoops" errors and missing data, preventing them from completing stock management and order packing actions. The issue affected a subset of customers and required manual syncing by Customer Support to restore functionality when reported. The service has been resolved and returned to normal operation with continued monitoring to prevent recurrence.

Sage experienced a 49.7-hour partial outage affecting E-Invoicing services across multiple products (Sage Active, Sage Connect, Sage for Accountants, and E-Invoicing Portal), where customers in France were unable to complete E-Invoicing onboarding due to SIREN registration failures in the PPF directory. Sage temporarily disabled E-Invoicing functionality to prevent further onboarding failures while working with their partner to resolve an issue on the Chorus Pro/PPF side. The service was fully restored and returned to normal operation with close monitoring to prevent recurrence.

Sage DPW Cloud experienced a partial outage that prevented a subset of customers in Austria from accessing the service for 3.9 hours. The issue was identified and investigated by the Sage team, who then monitored the service to ensure stable performance. The service was fully resolved and returned to normal operation.