Jitterbit incident

LATAM: Wevo iPaaS slowness when turning integrations (Flow) to ON state

Minor Resolved View vendor source →

Jitterbit experienced a minor incident on October 20, 2025 affecting Flow Runtime Core and Wevo iPaaS Portal and 1 more component, lasting 5h 5m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 04:54 PM UTC
Resolved
Oct 20, 2025, 10:00 PM UTC
Duration
5h 5m
Detected by Pingoru
Oct 20, 2025, 04:54 PM UTC

Affected components

Flow Runtime CoreWevo iPaaS PortalOn-Premise Agent

Update timeline

  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.