- Detected by Pingoru
- Oct 05, 2026, 06:13 PM UTC
- Resolved
- Oct 05, 2026, 06:13 PM UTC
- Duration
- —
Affected: Kinetic – G – Life Sciences – AustraliaKineticKinetic
Timeline · 1 update
-
in progress Oct 21, 2026, 11:00 AM UTC
Routine monthly operating system patches and security updates will be applied to Kinetic – G – Life Sciences – Australia. During this period, we will implement critical updates to our server operating systems to ensure the security and stability of our infrastructure. During the maintenance window, your system will experience temporary downtime and possible intermittent access issues. From: Wednesday, October 21, 10:00 PM Local Datacenter Time To: Thursday, October 22, 4:00 AM Local Datacenter Time A notification will be posted once the maintenance has been completed.
Read the full incident report →
- Detected by Pingoru
- Oct 05, 2026, 06:13 PM UTC
- Resolved
- Oct 05, 2026, 06:13 PM UTC
- Duration
- —
Affected: Prophet 21 - AustraliaProphet 21
Timeline · 1 update
-
resolved Oct 21, 2026, 11:00 AM UTC
Routine monthly operating system patches and security updates will be applied to Prophet 21 - Australia Non-Production SQL servers. During this period, we will implement critical updates to our server operating systems to ensure the security and stability of our infrastructure. During the maintenance window, your system will experience temporary downtime and possible intermittent access issues. From: Wednesday, October 21, 10:00 PM Local Datacenter Time To: Thursday, October 22, 4:00 AM Local Datacenter Time A notification will be posted once the maintenance has been completed.
Read the full incident report →
- Detected by Pingoru
- Oct 05, 2026, 02:19 PM UTC
- Resolved
- Oct 05, 2026, 03:32 PM UTC
- Duration
- 1h 13m
Affected: Epicor Identity Provider (IdP)
Timeline · 3 updates
-
identified Oct 05, 2026, 02:19 PM UTC
We’re currently experiencing an issue with our Identity Provider (IDP), which may prevent users from signing in or accessing connected applications. Our team is actively investigating and working to restore service. We’ll share another update as soon as more information is available. Thank you for your patience.
-
identified Oct 05, 2026, 03:15 PM UTC
The incident affecting the Identity Provider (IDP) has been resolved. Service has been restored, and our teams have confirmed that the system is operating normally. We apologize for the disruption and appreciate your patience while we worked to restore service. If you continue to experience any issues, please raise a ticket through the EpicCare Service Portal.
-
resolved Oct 05, 2026, 03:32 PM UTC
We are pleased to inform you that the issue has been resolved. Thank you for your patience during this time. Please do not hesitate to raise a ticket in EpicCare if you have any concerns or questions.
Read the full incident report →
- Detected by Pingoru
- Oct 05, 2026, 09:48 AM UTC
- Resolved
- Oct 06, 2026, 01:26 PM UTC
- Duration
- 1d 3h
Affected: Epicor EDITDX VAN - AMER
Timeline · 2 updates
-
investigating Oct 05, 2026, 09:48 AM UTC
We are currently experiencing document processing delays in our production environment. Documents continue to process; however, some customers may experience longer-than-usual delivery times. We apologize for the inconvenience and appreciate your patience. We will provide updates as more information becomes available and notify you once normal processing has been restored.
-
resolved Oct 06, 2026, 01:26 PM UTC
The issue impacting transaction processing has been resolved as of 7:30 PM EST on October 5, 2026. We are currently not observing any processing backlogs, and transaction flow has returned to normal operating levels. Our Support and Development teams are actively investigating the root cause of the incident and are working on a Root Cause Analysis (RCA). We will provide additional updates as they become available. We appreciate your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Oct 01, 2026, 06:04 AM UTC
- Resolved
- Oct 01, 2026, 06:04 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Oct 18, 2026, 03:00 AM UTC
Routine monthly operating system patches and security updates will be applied to Kinetic - Enterprise. During this period, we will implement critical updates to our server operating systems to ensure the security and stability of our infrastructure. During the maintenance window, your system will experience temporary downtime and possible intermittent access issues. From: Saturday, October 17, 10:00 PM Local Datacenter Time To: Sunday, October 18, 4:00 AM Local Datacenter Time A notification will be posted once the maintenance has been completed.
Read the full incident report →
- Detected by Pingoru
- Oct 01, 2026, 06:04 AM UTC
- Resolved
- Oct 01, 2026, 06:04 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Oct 18, 2026, 04:59 AM UTC
Routine monthly operating system patches and security updates will be applied to Prophet 21 - Americas. During this period, we will implement critical updates to our server operating systems to ensure the security and stability of our infrastructure. During the maintenance window, your system will experience temporary downtime and possible intermittent access issues. From: Saturday, October 17, 11:59 PM Local Datacenter Time To: Sunday, October 18, 4:00 AM Local Datacenter Time A notification will be posted once the maintenance has been completed.
Read the full incident report →
- Detected by Pingoru
- Oct 01, 2026, 06:04 AM UTC
- Resolved
- Oct 01, 2026, 06:04 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Oct 18, 2026, 04:59 AM UTC
Routine monthly operating system patches and security updates will be applied to Prophet 21 - Canada. During this period, we will implement critical updates to our server operating systems to ensure the security and stability of our infrastructure. During the maintenance window, your system will experience temporary downtime and possible intermittent access issues. From: Saturday, October 17, 11:59 PM Local Datacenter Time To: Sunday, October 18, 4:00 AM Local Datacenter Time A notification will be posted once the maintenance has been completed.
Read the full incident report →
- Detected by Pingoru
- Oct 01, 2026, 06:04 AM UTC
- Resolved
- Oct 01, 2026, 06:04 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Oct 18, 2026, 04:59 AM UTC
Routine monthly operating system patches and security updates will be applied to Prophet 21 - Enterprise. During this period, we will implement critical updates to our server operating systems to ensure the security and stability of our infrastructure. During the maintenance window, your system will experience temporary downtime and possible intermittent access issues. From: Saturday, October 17, 11:59 PM Local Datacenter Time To: Sunday, October 18, 4:00 AM Local Datacenter Time A notification will be posted once the maintenance has been completed.
Read the full incident report →
- Detected by Pingoru
- Sep 30, 2026, 02:36 PM UTC
- Resolved
- Sep 30, 2026, 09:27 PM UTC
- Duration
- 6h 51m
Affected: Epicor CPQEpicor CPQ - AmericasEpicor CPQEpicor CPQEpicor CPQ - AmericasEpicor CPQ - Americas
Timeline · 2 updates
-
investigating Sep 30, 2026, 02:36 PM UTC
We are currently investigating delays in completing output builds. During this time, outputs may take significantly longer time to process. Updates will be provided when the issue improves. Thank you for your patience.
-
resolved Sep 30, 2026, 09:27 PM UTC
The delays in completing output builds have been resolved. Service has returned to expected levels, and our teams have confirmed stability through monitoring. We apologize for the disruption and appreciate your patience while we worked to restore normal performance. If you continue to experience any issues, please raise a ticket through the EpicCare Service Portal.
Read the full incident report →
- Detected by Pingoru
- Sep 23, 2026, 06:23 PM UTC
- Resolved
- Sep 23, 2026, 10:45 PM UTC
- Duration
- 4h 22m
Affected: KineticKineticKineticKineticKineticKineticKineticKineticKinetic - AmericasKineticKineticKineticKineticKineticKinetic - AmericasKineticKineticKineticKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - Americas
Timeline · 9 updates
Read the full incident report →
Notice September 23, 2026 - Detected by Pingoru
- Sep 23, 2026, 01:15 PM UTC
- Resolved
- Sep 23, 2026, 01:15 PM UTC
- Duration
- —
Affected: Epicor CPQEpicor CPQ - AmericasEpicor CPQ - Europe
Timeline · 1 update
-
investigating Sep 23, 2026, 01:15 PM UTC
Dear Customer, The latest Epicor CPQ release is now available. You can view the final release notes here: Release Notes – Epicor CPQ Yours, Epicor CPQ Operations
Read the full incident report →
Notice September 23, 2026 - Detected by Pingoru
- Sep 23, 2026, 12:35 AM UTC
- Resolved
- Sep 23, 2026, 12:35 AM UTC
- Duration
- —
Affected: Epicor CPQEpicor CPQ - AmericasEpicor CPQ - Europe
Timeline · 1 update
-
investigating Sep 23, 2026, 12:35 AM UTC
Dear Customer, A release has been scheduled for Epicor CPQ, updating all customers to the newest version of the platform. You can view the pre-release notes here: Release Notes – Epicor CPQ Estimated Release Date: Tuesday, September 22nd Downtime: No downtime is expected Yours, Epicor CPQ Operations
Read the full incident report →
- Detected by Pingoru
- Sep 22, 2026, 01:43 PM UTC
- Resolved
- Sep 22, 2026, 02:25 PM UTC
- Duration
- 42m
Affected: EagleEagleEagleEagle - EastEagle - EastEagleEagle - EastEagle - EastEagleEagleEagleEagle - EastEagleEagle - EastEagleEagle - EastEagleEagle - EastEagleEagle - EastEagle - EastEagleEagle - EastEagle - East
Timeline · 2 updates
-
identified Sep 22, 2026, 01:43 PM UTC
We are currently investigating an incident that is impacting a subset of customers in your region. We apologize for any inconvenience this may cause and are working to resolve the issue as quickly as possible. We will provide updates as we have them, and appreciate your patience while we work to resolve the issue.
-
resolved Sep 22, 2026, 02:25 PM UTC
We are pleased to inform you that the issue has been resolved. Thank you for your patience during this time. Please do not hesitate to raise a ticket in EpicCare if you have any concerns or questions.
Read the full incident report →
- Detected by Pingoru
- Sep 21, 2026, 09:00 AM UTC
- Resolved
- Sep 21, 2026, 09:01 AM UTC
- Duration
- 1m
Affected: WorkatoRecipe runtimeWorkbotAPI gatewayEmail notificationsWebhook ingestionOn-premise connectivityWebsiteRecipe job processingWorkbot for WorkplaceWorkbot for SlackWorkbot for TeamsAPI gatewayWorkatoWorkatoWorkatoRecipe runtimeWorkbotAPI gatewayEmail notificationsWebhook ingestionOn-premise connectivityWebsiteRecipe job processingWorkbot for WorkplaceWorkbot for SlackWorkbot for TeamsRecipe runtimeWorkbotAPI gatewayEmail notificationsWebhook ingestionOn-premise connectivityWebsiteRecipe job processingWorkbot for WorkplaceWorkbot for SlackWorkbot for TeamsWorkatoRecipe runtimeWorkbotEmail notificationsWebhook ingestionOn-premise connectivityWebsiteRecipe job processingWorkbot for WorkplaceWorkbot for SlackWorkbot for TeamsWorkatoRecipe runtimeWorkbotAPI gatewayEmail notificationsWebhook ingestionOn-premise connectivityWebsiteRecipe job processingWorkbot for WorkplaceWorkbot for SlackWorkbot for TeamsRecipe runtimeWorkbotAPI gatewayEmail notificationsWebhook ingestionOn-premise connectivityWebsiteRecipe job processingWorkbot for WorkplaceWorkbot for SlackWorkbot for Teams
Timeline · 2 updates
-
identified Sep 21, 2026, 09:00 AM UTC
Between approximately 09:00 AM UTC on September 21 and 02:57 PM UTC on September 23, 2026, the Workato platform experienced an intermittent performance degradation in Workato FileStorage. In addition to the Workato FileStorage connector, features that use FileStorage internally were also affected. These include SQL Collection, Data Tables, PDF Tools, API Platform, data transformations, and some database connector actions, such as Snowflake file uploads. Customers may have observed these steps taking longer than usual to complete, and some recipe jobs may have failed with timeout errors. The issue has been resolved. Failed jobs may be repeated as needed. Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance regarding this incident.
-
resolved Sep 21, 2026, 09:01 AM UTC
Incident closed.
Read the full incident report →
- Detected by Pingoru
- Sep 21, 2026, 01:12 AM UTC
- Resolved
- Sep 21, 2026, 03:05 AM UTC
- Duration
- 1h 53m
Affected: KineticKinetic - MT/ExpressKineticKineticKineticKineticKineticKineticKineticKineticKineticKinetic - MT/ExpressKineticKineticKineticKineticKineticKineticKineticKinetic - MT/ExpressKineticKineticKineticKinetic - MT/ExpressKinetic - MT/ExpressKinetic - MT/ExpressKinetic - MT/ExpressKinetic - MT/Express
Timeline · 6 updates
-
identified Sep 21, 2026, 01:12 AM UTC
We are currently investigating an incident affecting availability of Kinetic Multi-Tenant for some customers in US. Our technical teams are fully engaged and working to restore service as quickly as possible. We apologize for the impact to your operations and will provide the next update within 60 minutes, or sooner if there is a significant change.
-
identified Sep 21, 2026, 01:44 AM UTC
We are continuing to investigate the incident affecting availability of Kinetic Multi-Tenant for some customers in US. The root cause has not yet been confirmed. Our teams are continuing to review service health, system activity, and related components to determine the cause and restore service. We apologize for the ongoing disruption and will provide the next update within 30 minutes, or sooner if there is a significant change.
-
identified Sep 21, 2026, 02:07 AM UTC
We are actively investigating an availability issue affecting some Kinetic Multi-Tenant customers in the US. While the root cause remains unconfirmed, our teams are reviewing service health, system activity, and related components to identify the issue and restore service. We apologize for the disruption and will share another update within 30 minutes, or sooner if there is a significant change.
-
identified Sep 21, 2026, 02:25 AM UTC
We have identified the root cause of the incident affecting availability of Kinetic Multi-Tenant for some customers in US. Our technical teams are implementing corrective actions to restore service. We apologize for the continued disruption and will provide the next update within 30 minutes, or sooner if service is restored.
-
identified Sep 21, 2026, 02:49 AM UTC
The root cause of the availability issue impacting a subset of Kinetic Multi-Tenant customers in the US has been identified. Our technical teams are actively applying corrective measures and working to restore full service as quickly as possible. We apologize for the continued disruption and appreciate your patience. The next update will be provided within 30 minutes, or sooner if service is fully restored.
-
resolved Sep 21, 2026, 03:05 AM UTC
The incident affecting availability of Kinetic Multi-Tenant for some customers in US has been resolved. Service has been restored, and our teams have confirmed that the system is operating normally. We apologize for the disruption and appreciate your patience while we worked to restore service. If you continue to experience any issues, please raise a ticket through the EpicCare Service Portal.
Read the full incident report →
- Detected by Pingoru
- Sep 20, 2026, 02:29 PM UTC
- Resolved
- Sep 20, 2026, 04:19 PM UTC
- Duration
- 1h 50m
Affected: Prophet 21Prophet 21 - AmericasProphet 21Prophet 21Prophet 21Prophet 21 - AmericasProphet 21 - AmericasProphet 21 - AmericasProphet 21Prophet 21 - AmericasProphet 21Prophet 21Prophet 21Prophet 21 - AmericasProphet 21 - AmericasProphet 21 - Americas
Timeline · 3 updates
-
identified Sep 20, 2026, 02:29 PM UTC
We are currently investigating an incident affecting availability of P21 for some customers in Americas Production. Our technical teams are fully engaged and working to restore service as quickly as possible. We apologize for the impact to your operations and will provide the next update within 60 minutes, or sooner if there is a significant change.
-
identified Sep 20, 2026, 03:28 PM UTC
We have identified the root cause of the incident affecting availability of P21 Public cloud for some customers in P21 Americas Production. Our technical teams are implementing corrective actions to restore service. We apologize for the continued disruption and will provide the next update within 30 minutes, or sooner if service is restored.
-
resolved Sep 20, 2026, 04:19 PM UTC
The incident affecting availability of P21 Public Cloud for some customers in the P21 US region has been resolved. Service has been restored, and our teams have confirmed that the system is operating normally. We apologize for the disruption and appreciate your patience while we worked to restore service. If you continue to experience any issues, please raise a ticket through the EpicCare Service Portal.
Read the full incident report →
- Detected by Pingoru
- Sep 20, 2026, 01:51 PM UTC
- Resolved
- Sep 20, 2026, 07:50 PM UTC
- Duration
- 5h 59m
Affected: Kinetic - AmericasKineticKineticKineticKineticKineticKineticKineticKineticKineticKinetic - AmericasKineticKineticKineticKineticKineticKineticKineticKineticKineticKineticKinetic - AmericasKineticKineticKineticKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - Americas
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- Sep 16, 2026, 09:28 AM UTC
- Resolved
- Sep 16, 2026, 05:20 PM UTC
- Duration
- 7h 52m
Affected: WorkatoAPI gatewayRecipe runtimeWorkbotAPI gatewayEmail notificationsWebhook ingestionOn-premise connectivityWebsiteRecipe job processingWorkbot for WorkplaceWorkbot for SlackWorkbot for TeamsWorkatoWorkatoRecipe runtimeWorkbotEmail notificationsWebhook ingestionOn-premise connectivityWebsiteRecipe job processingWorkbot for WorkplaceWorkbot for SlackWorkbot for TeamsWorkatoRecipe runtimeWorkbotAPI gatewayEmail notificationsWebhook ingestionOn-premise connectivityWebsiteRecipe job processingWorkbot for WorkplaceWorkbot for SlackWorkbot for TeamsRecipe runtimeWorkbotAPI gatewayEmail notificationsWebhook ingestionOn-premise connectivityWebsiteRecipe job processingWorkbot for WorkplaceWorkbot for SlackWorkbot for Teams
Timeline · 3 updates
-
identified Sep 16, 2026, 09:28 AM UTC
We have identified an issue affecting Workato's Salesforce connector. Customers may observe errors (such as "503 Service Unavailable") in Salesforce actions, recipe job failures, and delays in Salesforce-triggered jobs. This is caused by an ongoing Salesforce service disruption affecting multiple instances across all regions. We are actively monitoring Salesforce's recovery and our platform's error rates. We will share additional information as soon as it is available.
-
monitoring Sep 16, 2026, 11:15 AM UTC
We are continuing to monitor Salesforce's recovery and our platform's error rates. We will share additional information as soon as it is available.
-
resolved Sep 16, 2026, 05:20 PM UTC
Salesforce has completed recovery of its platform and the Salesforce connector, including actions and triggers, should no longer experience any errors. If you continue to experience any issues, please contact Workato Support at https://support.workato.com.
Read the full incident report →
- Detected by Pingoru
- Sep 15, 2026, 05:33 AM UTC
- Resolved
- Sep 15, 2026, 06:01 AM UTC
- Duration
- 28m
Affected: KineticKinetic - United Arab EmiratesKineticKineticKineticKinetic - United Arab EmiratesKineticKineticKineticKineticKineticKineticKineticKinetic - United Arab EmiratesKineticKineticKineticKineticKinetic - United Arab EmiratesKineticKineticKinetic - United Arab EmiratesKineticKineticKinetic - United Arab EmiratesKinetic - United Arab EmiratesKineticKinetic - United Arab EmiratesKinetic - United Arab EmiratesKinetic - United Arab EmiratesKinetic - United Arab EmiratesKinetic - United Arab EmiratesKinetic - United Arab EmiratesKinetic - United Arab EmiratesKinetic - United Arab EmiratesKinetic - United Arab EmiratesKinetic - United Arab EmiratesKinetic - United Arab Emirates
Timeline · 3 updates
-
identified Sep 15, 2026, 05:33 AM UTC
We are currently investigating a printing outage that is impacting a subset of customers in your region. We apologize for any inconvenience this may cause and are working to resolve the issue as quickly as possible. We will provide updates as we have them, and appreciate your patience while we work to resolve the issue.
-
identified Sep 15, 2026, 05:58 AM UTC
We have identified the root cause of the incident affecting printing functionality in Kinetic for some customers in United Arab Emirates. Our technical teams are implementing corrective actions to restore printing services. Affected customers may continue to experience failed, delayed, or pending print jobs while remediation is in progress. We will provide the next update within 30 minutes, or sooner if printing functionality is restored.
-
resolved Sep 15, 2026, 06:01 AM UTC
The incident affecting printing functionality in Kinetic for some customers in UAE has been resolved. Printing services have been restored, and our teams have confirmed that print jobs are processing successfully. We apologize for the disruption and appreciate your patience while we worked to restore this functionality. If you continue to experience any printing issues, please raise a ticket through the EpicCare Service Portal.
Read the full incident report →
- Detected by Pingoru
- Sep 08, 2026, 03:44 PM UTC
- Resolved
- Sep 08, 2026, 08:22 PM UTC
- Duration
- 4h 38m
Affected: Kinetic - AmericasKineticKineticKineticKineticKineticKineticKineticKinetic - AmericasKineticKinetic - AmericasKineticKineticKineticKineticKineticKinetic - AmericasKinetic - AmericasKineticKineticKinetic - AmericasKinetic - AmericasKinetic - AmericasKineticKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - Americas
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Sep 07, 2026, 11:00 PM UTC
- Resolved
- Sep 07, 2026, 11:01 PM UTC
- Duration
- 1m
Affected: WorkatoRecipe runtimeWorkbotAPI gatewayEmail notificationsWebhook ingestionOn-premise connectivityWebsiteRecipe job processingWorkbot for WorkplaceWorkbot for SlackWorkbot for Teams
Timeline · 2 updates
-
identified Sep 07, 2026, 11:00 PM UTC
Between approximately 12:18 PM UTC on September 7 and 12:13 PM UTC on September 9, 2026, the Workato platform experienced a performance degradation affecting the Box connector. Customers may have observed missed or delayed trigger events in recipes using the Box New File, New CSV File, or New/Updated CSV File triggers, caused by an error in event-filtering logic. Recipes that reached the consecutive trigger error threshold may have been stopped automatically. The issue has been resolved and the Box connector is operating as expected. Any stopped recipes may be restarted as required. Please contact Workato Support (https://support.workato.com) or your assigned CSM if you have any questions or require assistance regarding this incident.
-
resolved Sep 07, 2026, 11:01 PM UTC
Incident closed.
Read the full incident report →
- Detected by Pingoru
- Sep 03, 2026, 08:42 PM UTC
- Resolved
- Sep 03, 2026, 08:56 PM UTC
- Duration
- 14m
Affected: EagleEagleEagleEagleEagleEagleEagle - WestEagle - WestEagle - WestEagle - West
Timeline · 2 updates
-
investigating Sep 03, 2026, 08:42 PM UTC
We are currently investigating an incident that is impacting a subset of customers in your region. We apologize for any inconvenience this may cause and are working to resolve the issue as quickly as possible. We will provide updates as we have them, and appreciate your patience while we work to resolve the issue.
-
resolved Sep 03, 2026, 08:56 PM UTC
We are pleased to inform you that the issue has been resolved. Thank you for your patience during this time. Please do not hesitate to raise a ticket in EpicCare if you have any concerns or questions.
Read the full incident report →
- Detected by Pingoru
- Sep 02, 2026, 04:45 PM UTC
- Resolved
- Sep 02, 2026, 05:32 PM UTC
- Duration
- 47m
Affected: KineticKinetic - AmericasKineticKineticKineticKineticKinetic - AmericasKinetic - AmericasKineticKineticKineticKineticKineticKinetic - AmericasKinetic - AmericasKineticKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - AmericasKinetic - Americas
Timeline · 2 updates
-
investigating Sep 02, 2026, 04:45 PM UTC
We are currently investigating a printing outage that is impacting a subset of customers in your region. We apologize for any inconvenience this may cause and are working to resolve the issue as quickly as possible. We will provide updates as we have them, and appreciate your patience while we work to resolve the issue.
-
resolved Sep 02, 2026, 05:32 PM UTC
We are pleased to inform you that the issue has been resolved.Thank you for your patience during this time. Please do not hesitate to raise a ticket in EpicCare if you have any concerns or questions.
Read the full incident report →
- Detected by Pingoru
- Sep 01, 2026, 10:05 PM UTC
- Resolved
- Sep 02, 2026, 04:15 AM UTC
- Duration
- 6h 10m
Affected: WorkatoRecipe runtimeWorkbotAPI gatewayEmail notificationsWebhook ingestionOn-premise connectivityWebsiteRecipe job processingWorkbot for WorkplaceWorkbot for SlackWorkbot for TeamsWorkatoRecipe runtimeWorkbotAPI gatewayEmail notificationsWebhook ingestionOn-premise connectivityWebsiteRecipe job processingWorkbot for WorkplaceWorkbot for SlackWorkbot for TeamsWorkatoRecipe runtimeWorkbotAPI gatewayEmail notificationsWebhook ingestionOn-premise connectivityWebsiteRecipe job processingWorkbot for WorkplaceWorkbot for SlackWorkbot for TeamsWorkatoWorkatoRecipe runtimeWorkbotAPI gatewayEmail notificationsWebhook ingestionOn-premise connectivityWebsiteRecipe job processingWorkbot for WorkplaceWorkbot for SlackWorkbot for TeamsRecipe runtimeWorkbotAPI gatewayEmail notificationsWebhook ingestionOn-premise connectivityWebsiteRecipe job processingWorkbot for WorkplaceWorkbot for SlackWorkbot for Teams
Timeline · 5 updates
-
investigating Sep 01, 2026, 10:05 PM UTC
We are currently investigating issues related to Workato's QuickBooks Online connector. Customers may observe errors in QuickBooks Online actions, while triggers may experience delays in job creation. We will share additional information as soon as it is available.
-
identified Sep 01, 2026, 10:11 PM UTC
We have identified the underlying cause of the issue and are actively working on remediation. Workato's QuickBooks Online connector is experiencing issues owing to the external service provider's API degradation.
-
monitoring Sep 01, 2026, 10:58 PM UTC
Our team has taken steps to remediate the issue and is seeing improvement. We are continuing to monitor the platform as it recovers.
-
monitoring Sep 02, 2026, 01:40 AM UTC
Recipes using the QuickBooks Online connector continue to encounter errors. This continues to track the external service provider's ongoing API degradation, and the provider has reported that a fix is in deployment on their side. We will keep this incident open and continue monitoring until connector error rates return to normal levels.
-
resolved Sep 02, 2026, 04:15 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 31, 2026, 05:17 PM UTC
- Resolved
- Aug 31, 2026, 05:17 PM UTC
- Duration
- —
Affected: Kinetic - AmericasKinetic - United Arab EmiratesKinetic - AustraliaKinetic - GermanyKinetic - SingaporeKinetic - IndiaKinetic - UKKineticKinetic - Canada
Timeline · 1 update
-
investigating Aug 31, 2026, 05:17 PM UTC
We are currently experiencing failures in CMP operations due to an ongoing Azure DevOps service degradation at Microsoft. Actions such as DMR, Task Agent Restart, Refresh, Update, Site Restart and Hotfix may not complete successfully until the upstream issue is resolved. Microsoft engineers have identified a configuration change that triggered this incident. They are actively reverting the change and monitoring the impact.
Read the full incident report →