Jitterbit Outage History

Started Jul 21, 2026, 06:49 PM UTC· resolved Jul 21, 2026, 07:08 PM UTC

1. investigating Jul 21, 2026, 06:49 PM UTC

   We are currently investigating an issue with Cloud Agent degradation causing sporadic API timeout errors.

2. resolved Jul 21, 2026, 07:08 PM UTC

   Service has recovered. We will continue to monitor.

Read the full incident report →

Started Jun 24, 2026, 01:04 PM UTC· resolved Jun 24, 2026, 03:28 PM UTC

1. investigating Jun 24, 2026, 01:04 PM UTC

   We are currently experiencing an issue with some scheduled operations not being started in the EMEA Sandbox Cloud Agents

2. monitoring Jun 24, 2026, 01:36 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Jun 24, 2026, 03:28 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2026, 06:37 PM UTC· resolved Jun 13, 2026, 11:10 AM UTC

1. investigating Jun 12, 2026, 06:37 PM UTC

   We are currently investigating an issue affecting the Wevo iPaaS platform in the LATAM region. Updates will be provided here as they become available.

2. monitoring Jun 12, 2026, 07:38 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Jun 13, 2026, 11:10 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 08, 2026, 02:21 AM UTC· resolved May 08, 2026, 05:25 AM UTC

1. investigating May 08, 2026, 02:21 AM UTC

   We are currently experiencing degraded performance in our Harmony platform in the NA (East) region. Please check back for updates.

2. investigating May 08, 2026, 02:56 AM UTC

   We are continuing to investigate this issue.

3. investigating May 08, 2026, 03:19 AM UTC

   We are continuing to investigate this issue.

4. monitoring May 08, 2026, 04:06 AM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved May 08, 2026, 05:25 AM UTC

   The issue has been mitigated.

6. postmortem May 08, 2026, 07:28 PM UTC

   | | | | --- | --- | | Product | Jitterbit iPaaS | | Issue | Jitterbit iPaaS degradation that caused operations to fail or be delayed. | | Impact | Major | | Services Impacted | The outage affected multiple services including 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 |

Read the full incident report →

Started Apr 16, 2026, 01:42 PM UTC· resolved Apr 16, 2026, 04:46 PM UTC

1. investigating Apr 16, 2026, 01:42 PM UTC

   We are currently experiencing degraded performance in our EMEA Harmony (West) zone. Please check back for updates.

2. monitoring Apr 16, 2026, 03:44 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Apr 16, 2026, 04:46 PM UTC

   This incident has been resolved.

4. postmortem Apr 16, 2026, 08:08 PM UTC

   | **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. |

Read the full incident report →

Started Apr 09, 2026, 02:35 PM UTC· resolved Apr 09, 2026, 04:05 PM UTC

1. investigating Apr 09, 2026, 02:35 PM UTC

   We are currently investigating missing API logs in the API manager

2. identified Apr 09, 2026, 02:43 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Apr 09, 2026, 03:03 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Apr 09, 2026, 04:05 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 26, 2026, 05:17 PM UTC· resolved Feb 27, 2026, 10:08 PM UTC

1. investigating Feb 26, 2026, 05:17 PM UTC

   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.

2. identified Feb 26, 2026, 10:42 PM UTC

   The issue has been identified and a fix is being implemented.

3. resolved Feb 27, 2026, 10:08 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 14, 2025, 03:02 PM UTC· resolved Nov 14, 2025, 06:03 PM UTC

1. investigating Nov 14, 2025, 03:02 PM UTC

   We are currently experiencing degraded performance on our NA eiCloud API portal. Please check back for updates.

2. monitoring Nov 14, 2025, 05:01 PM UTC

   A fix has been implemented, and we are monitoring the results.

3. resolved Nov 14, 2025, 06:03 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 14, 2025, 10:21 AM UTC· resolved Nov 14, 2025, 11:54 AM UTC

1. investigating Nov 14, 2025, 10:21 AM UTC

   We are currently investigating this issue.

2. investigating Nov 14, 2025, 10:45 AM UTC

   We are continuing to investigate this issue.

3. monitoring Nov 14, 2025, 10:57 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Nov 14, 2025, 11:54 AM UTC

   This incident has been resolved.

5. postmortem Nov 14, 2025, 05:29 PM UTC

   **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.

Read the full incident report →

Started Nov 13, 2025, 06:12 PM UTC· resolved Nov 14, 2025, 12:19 AM UTC

1. investigating Nov 13, 2025, 06:12 PM UTC

   We are currently experiencing degraded performance on our NA UI/API. Please check back for updates.

2. investigating Nov 13, 2025, 07:19 PM UTC

   We are continuing to investigate this issue.

3. investigating Nov 13, 2025, 07:46 PM UTC

   We are continuing to investigate this issue.

4. identified Nov 13, 2025, 10:15 PM UTC

   The issue has been identified and a fix is being implemented.

5. monitoring Nov 13, 2025, 10:15 PM UTC

   A fix has been implemented and we are monitoring the results.

6. resolved Nov 14, 2025, 12:19 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 12, 2025, 08:56 PM UTC· resolved Nov 13, 2025, 12:50 AM UTC

1. investigating Nov 12, 2025, 08:56 PM UTC

   We are currently experiencing degraded performance on our NA API Gateway platforms. Please check back for updates.

2. investigating Nov 12, 2025, 09:02 PM UTC

   We are continuing to investigate this issue.

3. investigating Nov 12, 2025, 10:35 PM UTC

   We are continuing to investigate this issue. An update will be shared soon.

4. resolved Nov 13, 2025, 12:50 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 06:32 PM UTC· resolved Oct 20, 2025, 10:06 PM UTC

1. investigating Oct 20, 2025, 06:32 PM UTC

   We are currently investigating an issue with JitterbitMQ intermittent response.

2. identified Oct 20, 2025, 07:03 PM UTC

   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.

3. monitoring Oct 20, 2025, 09:35 PM UTC

   The issue with the third-party provider appears to be resolved, and we are currently monitoring the situation.

4. resolved Oct 20, 2025, 10:06 PM UTC

   This incident is resolved

Read the full incident report →

Started Oct 20, 2025, 04:54 PM UTC· resolved Oct 20, 2025, 10:00 PM UTC

1. identified Oct 20, 2025, 04:54 PM UTC

   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.

2. identified Oct 20, 2025, 05:52 PM UTC

   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.

3. identified Oct 20, 2025, 06:07 PM UTC

   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.

4. identified Oct 20, 2025, 06:30 PM UTC

   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

5. monitoring Oct 20, 2025, 08:19 PM UTC

   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.

6. monitoring Oct 20, 2025, 09:46 PM UTC

   The issue with our third-party cloud provider appears to be resolved, and we are currently monitoring the situation.

7. resolved Oct 20, 2025, 10:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 12, 2025, 03:24 PM UTC· resolved Sep 12, 2025, 03:41 PM UTC

1. investigating Sep 12, 2025, 03:24 PM UTC

   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.

2. monitoring Sep 12, 2025, 03:34 PM UTC

   We believe the Wevo iPaaS Platform is now accessible through the third-party internet provider VIVO. Our team continues to actively monitor the situation.

3. resolved Sep 12, 2025, 03:41 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 13, 2025, 12:10 PM UTC· resolved Aug 13, 2025, 01:29 PM UTC

1. investigating Aug 13, 2025, 12:10 PM UTC

   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.

2. identified Aug 13, 2025, 12:17 PM UTC

   The root cause of the issue has been identified, and our team is actively working on implementing a solution.

3. monitoring Aug 13, 2025, 12:54 PM UTC

   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.

4. resolved Aug 13, 2025, 01:29 PM UTC

   This incident has been resolved. The backlog of Flow Execution logs has been fully processed, and the system has returned to normal processing times.

Read the full incident report →

Started Jun 09, 2025, 07:55 AM UTC· resolved Jun 09, 2025, 08:19 AM UTC

1. investigating Jun 09, 2025, 07:55 AM UTC

   We are currently investigating slow EDI document processing in NA eiCloud. We will update when we have more information.

2. resolved Jun 09, 2025, 08:19 AM UTC

   Issue has been resolved and job processing has normalized.

Read the full incident report →

Started May 02, 2025, 11:36 AM UTC· resolved May 02, 2025, 12:49 PM UTC

1. investigating May 02, 2025, 11:36 AM UTC

   We are currently experiencing an issue causing the navigation from the Wevo iPaaS to be slow, which is also affecting some of the flow's execution.

2. identified May 02, 2025, 11:43 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring May 02, 2025, 11:45 AM UTC

   A fix has been implemented and we are monitoring the results.

4. identified May 02, 2025, 12:01 PM UTC

   The issue has been identified and a fix is being implemented.

5. identified May 02, 2025, 12:14 PM UTC

   We are continuing to work on a fix for this issue.

6. monitoring May 02, 2025, 12:30 PM UTC

   A fix has been implemented and we are monitoring the results.

7. monitoring May 02, 2025, 12:49 PM UTC

   We are continuing to monitor for any further issues.

8. resolved May 02, 2025, 12:49 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 22, 2025, 02:30 PM UTC· resolved Apr 22, 2025, 02:30 PM UTC

1. resolved Apr 22, 2025, 03:05 PM UTC

   We are investigating high response times in North America Harmony iPaaS

2. postmortem Apr 25, 2025, 08:00 PM UTC

   **Issue Summary:** Users experienced slowness across the platform, leading to performance degradation and latency in services. **Root Cause:** The slowness was traced to excessive resource consumption within the data layer of the platform. This was caused by a surge in typical queries which placed an load on backend data processing systems. **Impact:** * Noticeable performance lag for end-users interacting with the Frontend ~~platform~~. **Resolution:** The issue has been identified and isolated. A fix addressing the data layer’s handling of such high-volume queries is currently being implemented and is scheduled for deployment in an upcoming platform release.

Read the full incident report →

Started Apr 01, 2025, 07:30 PM UTC· resolved Apr 01, 2025, 10:40 PM UTC

1. investigating Apr 01, 2025, 07:30 PM UTC

   We are currently investigating this issue.

2. identified Apr 01, 2025, 08:09 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Apr 01, 2025, 10:32 PM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring Apr 01, 2025, 10:32 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Apr 01, 2025, 10:40 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 11, 2025, 10:49 AM UTC· resolved Mar 11, 2025, 11:15 AM UTC

1. investigating Mar 11, 2025, 10:49 AM UTC

   We are currently experiencing degraded performance in our EMEA Harmony (West) zone. Please check back for updates.

2. monitoring Mar 11, 2025, 10:57 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Mar 11, 2025, 11:15 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 03, 2025, 10:22 AM UTC· resolved Feb 04, 2025, 08:47 PM UTC

1. investigating Feb 03, 2025, 10:22 AM UTC

   We are currently experiencing a slowness while processing flows' execution logs. The execution logs will be delayed to be reflected in the Wevo iPaaS portal but no flows' executions are getting impacted, all flows are properly being executed as their schedules are configured.

2. identified Feb 03, 2025, 10:34 AM UTC

   The issue has been identified and the team is currently working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed.

3. identified Feb 03, 2025, 11:30 AM UTC

   The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed.

4. identified Feb 03, 2025, 12:30 PM UTC

   The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed.

5. identified Feb 03, 2025, 01:30 PM UTC

   The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed.

6. identified Feb 03, 2025, 02:38 PM UTC

   The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed.

7. identified Feb 03, 2025, 03:33 PM UTC

   The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed.

8. identified Feb 03, 2025, 04:33 PM UTC

   The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed. The flows execution haven't been impacted and are still running even though not reflected in the Wevo iPaaS portal.

9. identified Feb 03, 2025, 06:23 PM UTC

   The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed. The flows execution haven't been impacted and are still running even though not reflected in the Wevo iPaaS portal.

10. identified Feb 03, 2025, 09:32 PM UTC

    The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed. The flows execution haven't been impacted and are still running even though not reflected in the Wevo iPaaS portal.

11. identified Feb 03, 2025, 11:38 PM UTC

    The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed. The flows execution haven't been impacted and are still running even though not reflected in the Wevo iPaaS portal.

12. identified Feb 04, 2025, 12:31 AM UTC

    The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed. The flows execution haven't been impacted and are still running even though not reflected in the Wevo iPaaS portal.

13. monitoring Feb 04, 2025, 02:04 AM UTC

    A fix has been implemented and we are monitoring the results. Going forward, all the new flow's execution logs will be reflected in the Wevo iPaaS portal after the integration execution is finished. Please note that old execution logs may still be delayed to be visible.

14. identified Feb 04, 2025, 09:43 AM UTC

    We have identified a new delay to process flow's execution logs and the team is already working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed. The flow execution hasn't been impacted and is still running even though not reflected in the Wevo iPaaS portal.

15. identified Feb 04, 2025, 01:14 PM UTC

    We are continuing to work on a fix for this issue. A maintenance has been started in the Wevo iPaaS Cloud Database. There won't be any data loss during this process or impact during the flow execution.

16. monitoring Feb 04, 2025, 02:31 PM UTC

    The Wevo iPaaS Cloud Database maintenance is still in progress. Going forward, all the new flow's execution logs will be reflected in the Wevo iPaaS portal after the integration execution is finished. Please note that old execution logs may still be delayed to be visible since they are enqueued for processing as a backlog.

17. monitoring Feb 04, 2025, 03:33 PM UTC

    The Wevo iPaaS Cloud Database maintenance is still in progress. Going forward, all the new flow's execution logs will be reflected in the Wevo iPaaS portal after the integration execution is finished. Please note that old execution logs may still be delayed to be visible since they are enqueued for processing as a backlog.

18. monitoring Feb 04, 2025, 05:28 PM UTC

    The Wevo iPaaS Cloud Database maintenance is still in progress. Going forward, all the new flow's execution logs will be reflected in the Wevo iPaaS portal after the integration execution is finished. Please note that old execution logs may still be delayed to be visible since they are enqueued for processing as a backlog.

19. monitoring Feb 04, 2025, 07:47 PM UTC

    The Wevo iPaaS Cloud Database maintenance has been finished and all the new flow's execution logs will be reflected in the Wevo iPaaS portal after the flow execution is finished. We're currently working to process the delayed logs backlog from the past few days and monitoring the environment health.

20. resolved Feb 04, 2025, 08:47 PM UTC

    This incident has been resolved. All the new flow's execution logs are being reflected in the Wevo iPaaS portal as the integrations are executed. We expect to process the entire backlog in the next 72 hours.

Read the full incident report →

Started Dec 24, 2024, 06:22 PM UTC· resolved Dec 24, 2024, 09:47 PM UTC

1. investigating Dec 24, 2024, 07:22 PM UTC

   We are currently investigating this issue.

2. identified Dec 24, 2024, 07:47 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Dec 24, 2024, 08:30 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Dec 24, 2024, 09:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 13, 2024, 02:00 AM UTC· resolved Nov 13, 2024, 05:00 AM UTC

1. resolved Nov 13, 2024, 04:50 PM UTC

   New flow's execution were not triggered causing integrations not to run

Read the full incident report →