Sage Outage History

Sage 50 Cloud experienced a 6.3-hour partial outage where US customers were unable to provision new sites. The company identified the root cause, applied a fix to restore normal provisioning functionality, and worked to provision sites for customers who experienced failures during the incident. The service was fully resolved and performing as expected.

Sage People experienced a partial outage where the recruitment functionality stopped working for global customers, lasting approximately 140.6 hours. The issue was identified as affecting one specific area of the product while other components remained operational. The service was fully restored and returned to normal performance after the root cause was identified and fixed.

Sage experienced a major outage affecting their sage.com website globally for 8.9 hours, with customers unable to access the site and being presented with a maintenance page instead. The service was restored and returned to normal performance, with Sage monitoring closely to prevent recurrence.

Sage Active experienced a partial outage affecting the iOS mobile application for customers in France, Spain, the UK, Germany, and Romania, while other platforms continued to function normally. The issue prevented users from accessing the mobile app for approximately 22.4 hours. The problem was identified, fixed, and service was fully restored with normal performance.

Sage Active experienced a partial outage lasting 13 minutes. The service team investigated a potential issue affecting the Sage Active component. The incident was resolved after the investigation period.

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.

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.