51 incidente Jitterbit înregistrate începând din aprilie 2024, cu actualizări oficiale, componente afectate, durată și informații despre rezolvare.
În prezent investigăm o problemă cu degradarea agentului cloud care cauzează erori sporadice de temporizare.
Serviciul şi-a revenit. Vom continua să monitorizăm.
Traducere automată din actualizarea oficială a incidentului.
We are currently experiencing an issue with some scheduled operations not being started in the EMEA Sandbox Cloud Agents
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue affecting the Wevo iPaaS platform in the LATAM region. Updates will be provided here as they become available.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing degraded performance in our Harmony platform in the NA (East) region. Please check back for updates.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
The issue has been mitigated.
| | | | --- | --- | | Product | Jitterbit iPaaS | | Issue | Jitterbit iPaaS degradation that caused operations to fail or be delayed. | | Impact | Major | | Services Impacted | The outage affected multiple services impacting APIs and operations. | | Location | North America \(NA\) | | Problem Description | The issue was caused by a widespread issue with an upstream provider that degraded Jitterbit services. | | Timeline of Events \(UTC\) | Between 00:25 and 04:00 UTC, May 8, 2026 | | Root Cause | An upstream provider experienced an issue, resulting in the degradation of one of the availability zones. | | Action | Immediate Action: To restore functionality, we promptly transitioned services from the affected availability zone to alternate healthy zones. However, during this transition there was a backlog in processing that caused delays. Strategic Action: Conduct an investigation into accelerating the processing of queue backlogs during service transitions Additional alerting on queue backlogs |
We are currently experiencing degraded performance in our EMEA Harmony (West) zone. Please check back for updates.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
| **Root Cause Analysis** | | | --- | --- | | **Product** | Harmonhy iPaaS | | **Issue** | Degraded performance within Jitterbit iPaaS product, which resulted in delayed or failed operation executions. | | **Impact** | Major | | **Service Impact** | This outage affected running operations where the status was delayed. | | **Location** | EMEA | | **Problem Description** | Jitterbit identified a delay in its logging and status system. This caused some operations to appear stuck in 'submitted,' which blocked scheduled operations that were waiting for the previous step to finish. | | **Timeline of Events \(UTC\)** | Intermittent between 09:20 and 15:10 UTC, April 16, 2026 | | **Root Cause** | Increased data volume caused by a looping event that slowed status update frequency, causing a cascade of issues across several logging system components. | | **Action** | Immediate Action: Removed offending looping events that put undue strain on logging and status systems. Strategic Action: Deploy safeguards to prevent similar surges. Implement Read/Write separation to ensure high-volume read traffic does not contend with or degrade operation runtimes. Track non-terminal operation counts to identify and alert on processing delays in real-time. |
We are currently investigating an issue affecting the Wevo iPaaS platform in the LATAM region. Updates will be provided here as they become available
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating missing API logs in the API manager
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Please be advised that we are currently investigating a technical issue affecting the Harmony SAML login service. Some users may experience "Access Denied" errors or find themselves locked out of the system. Action Required: If you require immediate access and are unable to log in, please reach out to our Support Team ([email protected]). They are standing by to assist with an interim workaround until the primary login service is restored. We apologize for this interruption and are working to resolve the matter as a high priority.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating an issue affecting the Wevo iPaaS platform in the LATAM region. Updates will be provided here as they become available
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing degraded performance on our NA eiCloud API portal. Please check back for updates.
A fix has been implemented, and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
**Product:** Jitterbit iPaaS **Issue:** There was an issue impacting Jitterbit iPaaS in EMEA that impaired services for some customers. **Impact:** Major **Services Impacted:** This outage affected services across EMEA. Customers were unable to log in, and running of operations was impacted, including failures of API invocations on the API Manager. **Location:** EMEA **Problem Description** Our high-availability \(HA\) messaging system experienced an outage. The primary server experienced a memory capacity issue. The process stayed active and, therefore, did not fail-over. This prevented the backup server from fully taking over, causing a communication breakdown between microservices. **Timeline of Events \(UTC\)** 2025-11-14 08:36 - Messaging Broker 1 goes OOM and Broker 2 is promoted 2025-11-14 10:04 - Harmony Rest Service goes out of service 2025-11-14 10:41 - Broker 1 rebooted, service restored 2025-11-14 10:43 - Harmony Rest Service restored **Root Cause** Memory Exhaustion: The primary Message Broker experienced an Out of Memory \(OOM\) condition due to the exhaustion of its heap memory, leading to resource depletion and service degradation. HA Failover Failure: Although the system was in a degraded state, the primary broker's process did not completely fail or terminate. This state prevented the high-availability \(HA\) mechanism from successfully triggering the expected failover, leaving the backup server unable to assume the primary role and restore message communication between microservices. **Action** Immediate Action: The server was restarted, and the available memory \(heap space\) was increased. Strategic Action: Implement a process to ensure the backup server successfully takes over immediately in the event of memory exhaustion. Implement a tighter and deeper alerting for the messaging system focused on resource exhaustion and HA status.
We are currently experiencing degraded performance on our NA UI/API. Please check back for updates.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing degraded performance on our NA API Gateway platforms. Please check back for updates.
We are continuing to investigate this issue.
We are continuing to investigate this issue. An update will be shared soon.
This incident has been resolved.
We are currently investigating an issue with JitterbitMQ intermittent response.
The issue has been identified and is caused by an issue with our third-party cloud provider. Service remains intermittent as the broader issue is recovering.
The issue with the third-party provider appears to be resolved, and we are currently monitoring the situation.
This incident is resolved
We are currently experiencing an incident caused by an outage from our third-party cloud provider, which is impacting some services within the Wevo iPaaS Platform. All integrations are running normally at runtime without any execution impact. However, you may experience slowness or temporary failures when switching integrations (Flows) to the ON state. Our team is closely monitoring the situation, and we will share updates as soon as more information becomes available.
If you are a customer using the Wevo iPaaS On-Premise Agent or site-to-site VPN, you may experience network-related issues that could affect integrations (Flows) running against your private network. Our team is actively monitoring the situation and will provide updates as soon as we have more information.
We have also identified performance degradation affecting navigation within the Wevo iPaaS Portal, as well as some impact on integration (Flow) execution at runtime. Our team is actively investigating the issue and monitoring system performance closely. Updates will be provided as soon as more information becomes available.
At this point, all Wevo iPaaS On-Premise Agents are connected and operating normally, as well as all integrations (Flows) running at runtime. We would like to emphasize that this issue was caused by an outage from our third-party cloud provider. Please check the AWS Status page for the latest updates: https://health.aws.amazon.com/health/status
We are continuing to monitor the incident closely to identify any potential issues. We would like to reinforce that all integrations (Flows) are running normally at runtime, and all On-Premise Agents remain connected and fully operational.
The issue with our third-party cloud provider appears to be resolved, and we are currently monitoring the situation.
This incident has been resolved.
We are currently investigating an issue affecting the Wevo iPaaS platform in the LATAM region. Updates will be provided here as they become available.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Due to external factors, the Wevo iPaaS Platform is currently experiencing accessibility issues when accessed through the third-party internet provider VIVO. Access via other internet providers remains fully operational. We would like to emphasize that there are no issues with the Wevo iPaaS Platform itself. All integrations continue to run as expected, except for webhook requests originating from connections using the VIVO network.
We believe the Wevo iPaaS Platform is now accessible through the third-party internet provider VIVO. Our team continues to actively monitor the situation.
This incident has been resolved.
We are currently investigating an issue affecting the performance of Flow Execution log processing on the Wevo iPaaS Platform. As a result, it may appear that flows are not running as expected, even though they are being executed. We appreciate your patience while we work to resolve this issue.
The root cause of the issue has been identified, and our team is actively working on implementing a solution.
A fix has been implemented, and we are currently monitoring the results. Due to the earlier slowness in Flow Execution log processing, a backlog of logs has accumulated. All pending messages are expected to be fully processed over the next few hours. Our team will continue to monitor the platform closely until the backlog is cleared and normal processing times are fully restored.
This incident has been resolved. The backlog of Flow Execution logs has been fully processed, and the system has returned to normal processing times.
We are currently investigating an issue affecting the performance of Flow Execution log processing on the Wevo iPaaS Platform. As a result, it may appear that flows are not running as expected, even though they are being executed. We appreciate your patience while we work to resolve this issue.
The root cause of the issue has been identified, and our team is actively working on implementing a solution.
A fix has been implemented, and we are currently monitoring the results. Due to the earlier slowness in Flow Execution log processing, a backlog of logs has accumulated. All pending messages are expected to be fully processed over the next few hours. Our team will continue to monitor the platform closely until the backlog is cleared and normal processing times are fully restored.
This incident has been resolved. The backlog of Flow Execution logs has been fully processed, and the system has returned to normal processing times.
We are currently investigating an issue affecting the Wevo iPaaS platform in the LATAM region. Updates will be provided here as they become available.
The issue has been identified and the team is currently working on it.
We are currently monitoring the Wevo iPaaS environment for the LATAM region. No significant issues or impacts on customer integrations have been observed. Although certain infrastructure metrics have shown an unusual increase, we believe this is related to a spike in consumption and utilization from the Wevo iPaaS platform by our customers.
This incident has been resolved. We reaffirm that no issues or impacts on customer integrations were observed. We will take steps to further refine the thresholds used in our internal alerts and monitors.
