Total Synergy Outage History

The Synergy production platform has stabilised and the service is operating as expected. At this time, we have not been able to identify a definitive root cause. Our team will continue to investigate and closely monitor the environment to ensure ongoing stability. If you experience any further issues, please contact our support team.

We have identified the issue causing the 502 Bad Gateway error and resolved the problem.

The login and performance issues that Synergy users were experiencing from 7:30 AM AEDT, 9 February 2026 have been resolved. If you're still experiencing any performance issues, please contact Support for further investigation. Thank you for your patience and understanding during this time.

The issue has been marked as resolved by Microsoft and we will continue to monitor. Microsoft released the following information regarding the incident. Between 07:58 UTC on 07 February 2026 and 04:24 UTC on 08 February 2026, customers using multiple Azure services in the West US region may have experienced intermittent service unavailability, timeouts and/or higher than normal latency. The event began following an unexpected power interruption affecting a single West US datacenter, after which internal monitoring reported widespread device unreachability and downstream service degradation. Further information can be accessed by Microsoft users with Azure access here: https://status.cloud.microsoft/

The issue impacting the Global Search has now been resolved.

The issue impacting our UAT environment has been resolved and uat.totalsynergy.com is now available.

Between approximately 8:00 AM and 9:40 AM AEST on 14 April 2025, we experienced a login outage that prevented some users from accessing Total Synergy. Our development team has implemented a fix, and users are now able to log in successfully. A permanent hotfix will be released in the coming days to prevent this issue from reoccurring. We sincerely apologise for the disruption and appreciate your patience as we resolved the issue.

This incident has been resolved.

Microsoft released an update to the Issue ID EX921449 at 3:55 AM AEDT indicating they have addressed some issues that were delaying the script and have confirmed that 50 percent of all affected email messages have been released from quarantine. They are continuing to monitor the script as it progresses towards completion. As this update suggests, users with an email hosted by Microsoft Exchange Online should start to see their emails come through or re-appear over the course of the day. Please refer to Microsoft's Service Health page (as a Microsoft 365 Admin) or through your IT Partner for further updates. Thanks for your patience while we investigated this issue.

On Sunday, October 27, 07:00 AM AEDT / Saturday, October 26, 21:00 PM a technical fix was released to resolve this issue. Users that sync Synergy with QBO can now do so successfully. Thanks to QBO users who were patient while we worked on resolving this issue.

Between approximately 2:20PM - 2:40PM AEST today, we experienced a temporary issue with one of our servers, which impacted the generation of some invoices and report exports. Reports: If you attempted to generate a report during this period, reissue the report to resolve the issue. Invoices: If you attempted to generate invoices during this period, we recommend reviewing them and re-saving them if necessary. We apologise for any inconvenience and appreciate your understanding.

We are pleased to share that the Xero Connect compatibility issue impacting users on a Xero “Ultimate” plan has been resolved. Users can now successfully sync data between Synergy and Xero as expected. We apologise for any inconvenience and thank you for your patience.

This incident has been resolved.

This incident has been resolved.

On Monday, August 5th, Synergy experienced a significant performance issue that affected all users. This was resolved within 80 minutes of the initial report. However, report downloads were affected, creating a backlog that was resolved by 16:30 AEST. The system is now fully operational, and the initial cause and reporting are being closely monitored to ensure continued stability. We are currently dedicating additional efforts and resources to prevent similar incidents from occurring in the future. We understand that system availability and reporting are critical for our customers' workflows, especially following the end of the month. We apologise for any inconvenience this caused.