Zomentum Outage History
Zomentum is up right nowPingoru has recorded 41 incidents for Zomentum: 4 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 50 of 720 (7%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 515 (0%) |
Incidents, newest first
Notice April 13, 2026 Delayed ACH & BACS Payouts (Payment Processor Dependency) 2d 1h
Started Apr 13, 2026, 09:22 AM UTC· resolved Apr 15, 2026, 10:50 AM UTC
- investigating Apr 13, 2026, 09:22 AM UTC
We are currently experiencing delays in ACH and BACS payouts due to an issue with batch settlement reports from our payment processor. Settlement reports for batches are not being generated as expected. What’s happening: Automated batch settlement reports are not running for certain batches Manual attempts to trigger report generation are failing with a 500 server error This is preventing confirmation of settlement status for affected transactions Impact: ACH and BACS payouts are delayed for all customers Card transaction payouts are NOT impacted and continue as expected Current Status: Our internal systems and payout infrastructure have been verified to be functioning correctly We are actively working with our payment processor on root cause analysis and resolution Next Update: We will provide updates as soon as we receive meaningful progress. What you can expect: No action is required from your side at this time Our team is actively monitoring and will ensure payouts are processed as soon as settlement confirmation is restored
- resolved Apr 15, 2026, 10:50 AM UTC
Update: Resolved as of 10 AM IST The KYC review has been completed, and our payment partner has lifted the temporary suspension. Settlement reports have now resumed as expected, with batches received and processed successfully. Payouts are flowing normally again, with transactions already booked today. The remaining transactions have been processed through the standard pipeline. All systems are now fully operational, and no further manual intervention is required.
Minor March 11, 2026 Degraded Performance – Integrations, Automations, and Email Notifications 45m Integration API server
Started Mar 11, 2026, 04:55 PM UTC· resolved Mar 11, 2026, 05:40 PM UTC
- 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.
Critical February 17, 2026 QuickBooks Online Integration - Sync Disruption 2h 9m
Started Feb 17, 2026, 03:50 AM UTC· resolved Feb 17, 2026, 06:00 AM UTC
- investigating Feb 17, 2026, 03:50 AM UTC
We are aware that the QuickBooks Online integration for Zomentum Payments is currently experiencing a sync disruption. The issue began on February 16, 2026, and some customers may have received a notification from Intuit stating that "Zomentum Payments is offline." What's affected: - Payment and invoice data syncing between Zomentum Payments and QuickBooks Online What's NOT affected: - Zomentum Payments processing (collecting payments, sending invoices) - All other Zomentum platform functionality What we're doing: Our engineering team is actively investigating and working to restore the QuickBooks connection. No action is needed from customers at this time — once resolved, any queued sync data will be processed automatically. We will post updates here as we have more information.
- identified Feb 17, 2026, 04:38 AM UTC
We have identified the cause of the QuickBooks Online disruption that began on February 16, 2026. Our integration has reached the monthly QuickBooks API rate limit for our current plan tier. What's affected: - Payment and invoice data syncing between Zomentum Payments and QuickBooks Online - Payment collection for customers with QuickBooks Online integration enabled What's NOT affected: - Zomentum Payments processing for customers not using QuickBooks Online - All other Zomentum platform functionality What we're doing: We are working with Intuit to increase our API quota and restore full functionality. Once resolved, any queued sync data will be processed automatically. No action is needed from customers at this time. We will post updates as the situation progresses.
- monitoring Feb 17, 2026, 05:21 AM UTC
We have upgraded our QuickBooks API plan to resolve the rate limit issue that caused the disruption since February 16, 2026. Syncing and payment processing for QuickBooks Online customers should now be resuming. We are actively monitoring to confirm all services are operating normally. Any data that was queued during the downtime will be synced automatically. If you continue to experience issues, please contact our support team. We will post a final update once we have confirmed full recovery.
- resolved Feb 17, 2026, 06:00 AM UTC
The QuickBooks Online integration issue has been fully resolved. The API rate limit has been lifted, and all events that were queued during the outage have been successfully retried and processed. Payment processing and syncing for QuickBooks Online customers are fully operational. Thank you for your patience.
- postmortem Feb 17, 2026, 06:01 AM UTC
The Zomentum Payments integration with QuickBooks Online became unavailable after exceeding the monthly API rate limit \(500K calls\) on our Builder App plan. This blocked both QBO data syncing and payment collection for customers with QBO integration enabled. Approximately 350 events were queued during the outage. Timeline * Feb 16, 2026: QuickBooks API rate limit \(500K CorePlus calls\) exceeded. API began returning HTTP 429 with error code 3001 \("ThrottleExceeded"\). * Feb 17, 2026 4:13 AM: Intuit sent automated notification emails to connected QBO customers stating "Zomentum Payments is offline." * Feb 17, 2026: Issue identified as rate limit on Builder App tier. Decision made to upgrade to Intuit App Partner Program for unlimited API access. * Feb 17, 2026: Plan upgrade completed. Throttle lifted. All ~350 stuck events retried and processed successfully. Full functionality restored. Impact * ~350 events stuck in queue during the outage * Payment collection blocked for customers with QBO integration enabled * QBO data syncing paused for all connected customers * Customers received alarming "offline" notifications from Intuit Root Cause Our QuickBooks integration was on the Builder App plan, which has a monthly cap of 500K CorePlus API calls. As usage grew, we hit this limit mid-month, causing Intuit to block all API calls with a "Block All CorePlus for a Builder App" throttle policy. Resolution Upgraded to a higher-tier Intuit plan with increased API limits. All queued events were retried and succeeded once the throttle was lifted. Action Items 1. Implement API usage monitoring and alerting - Set up alerts when QBO API usage approaches the plan threshold \(e.g., at 80% and 90%\) to provide early warning before hitting limits. 2. Add rate limit handling in PaymentsQuickBooksClient - Implement backoff/retry logic and graceful degradation when receiving 429 responses instead of hard-failing. 3. Review API call efficiency - Audit current QBO API usage patterns to identify opportunities to reduce call volume \(batching, caching, eliminating redundant calls\). Lessons Learned * Third-party API rate limits are an operational risk that must be actively monitored. * Critical payment flows should not have hard dependencies on third-party sync operations. * Plan tier limits should be tracked as part of capacity planning.
Major December 29, 2025 Login Issue Via Microsoft Azure(365) SSO login 3h 14m
Started Dec 29, 2025, 12:44 PM UTC· resolved Dec 29, 2025, 03:59 PM UTC
- 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
Notice October 20, 2025 AWS outage resulting in degraded performance 2h 57m Main API server, Client application, Integration API server, Callback API server
Started Oct 20, 2025, 09:46 AM UTC· resolved Oct 20, 2025, 12:44 PM UTC
- 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.
Minor July 8, 2025 404/500 error 3m Main API server, Client application, Integration API server, Callback API server
Started Jul 08, 2025, 11:07 AM UTC· resolved Jul 08, 2025, 11:11 AM UTC
- 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.
Critical July 4, 2025 All Systems down due to a CORS error 37m Main API server, Client application
Started Jul 04, 2025, 09:42 AM UTC· resolved Jul 04, 2025, 10:19 AM UTC
- 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.
Notice February 14, 2025 Partner Align server is down 3h 11m
Started Feb 14, 2025, 06:35 AM UTC· resolved Feb 14, 2025, 09:46 AM UTC
- 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.