Zomentum Outage History
Zomentum is up right nowZomentum had 9 outages in the last 2 years totaling 62h 41m of downtime — averaging 0.4 incidents per month.
There were 9 Zomentum outages since July 5, 2024 totaling 62h 41m of downtime. Each is summarised below — incident details, duration, and resolution information.
Degraded Performance – Integrations, Automations, and Email Notifications
Affected: Integration API server
Timeline · 3 updates
- identified Mar 11, 2026, 04:55 PM UTC
We are currently experiencing a higher-than-usual number of reports related to the following areas of the platform: -PSA Integrations: Some users may notice delays or interruptions in data syncing with PSA integrations such as Halo, Autotask, and ConnectWise. -Automations: Certain automation workflows may not be triggering as expected. -Email Notifications: Email notifications for events such as document opens or status updates may not be sent or may be delayed. Our engineering team is actively investigating the root cause and working to restore full functionality as quickly as possible. We will continue to share updates on this page as we learn more.
- identified Mar 11, 2026, 04:57 PM UTC
We are continuing to work on a fix for this issue.
- resolved Mar 11, 2026, 05:40 PM UTC
The issue impacting PSA integrations , automation triggers, and certain email notifications has now been fully resolved. Our engineering team identified the root cause and implemented a fix to restore normal platform functionality. We will continue to monitor the system to ensure stability.
QuickBooks Online Integration - Sync Disruption
Timeline · 5 updates
Login Issue Via Microsoft Azure(365) SSO login
Timeline · 2 updates
- investigating Dec 29, 2025, 12:44 PM UTC
We are actively investigating the matter. Temporary workaround: We have temporarily disabled mandatory SSO from the backend. As a result, you should now be able to log in to Zomentum using your username and password. Thank you for your patience and understanding.
- resolved Dec 29, 2025, 03:59 PM UTC
The issue has been resolved successfully
AWS outage resulting in degraded performance
Affected: Main API serverClient applicationIntegration API serverCallback API server
Timeline · 3 updates
- investigating Oct 20, 2025, 09:46 AM UTC
We are currently investigating this issue.
- identified Oct 20, 2025, 09:54 AM UTC
After a thorough review, we identified that the root cause is related to a global outage currently affecting Amazon Web Services (AWS), which is impacting several major platforms worldwide. Our technical team is actively monitoring the situation to ensure there’s no disruption to our services.
- resolved Oct 20, 2025, 12:44 PM UTC
The issue has now been resolved, and our team is actively monitoring the situation to ensure continued stability.
404/500 error
Affected: Main API serverClient applicationIntegration API serverCallback API server
Timeline · 2 updates
- monitoring Jul 08, 2025, 11:07 AM UTC
A backend configuration issue had caused intermittent network errors. Our team has identified and resolved the root cause, and we are currently monitoring the systems closely to ensure everything continues to run smoothly.
- resolved Jul 08, 2025, 11:11 AM UTC
This incident has been resolved.
All Systems down due to a CORS error
Affected: Main API serverClient application
Timeline · 3 updates
- investigating Jul 04, 2025, 09:42 AM UTC
A back end configuration has resulted in Network Errors.
- monitoring Jul 04, 2025, 09:55 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 04, 2025, 10:19 AM UTC
This incident has been resolved.
Partner Align server is down
Timeline · 2 updates
- investigating Feb 14, 2025, 06:35 AM UTC
We are seeing elevated api failures in our Parner align servers
- resolved Feb 14, 2025, 09:46 AM UTC
This incident has been resolved.
Elevated API Errors
Affected: Main API server
Timeline · 2 updates
- investigating Jul 23, 2024, 10:54 AM UTC
We're experiencing an elevated level of API errors and are currently looking into the issue.
- resolved Jul 23, 2024, 11:08 AM UTC
This incident has been resolved.