Jitterbit Outage History

Jitterbit is up right now

Jitterbit had 30 outages in the last 2 years totaling 138h 2m of downtime — averaging 1.2 incidents per month.

There were 30 Jitterbit outages since August 14, 2024 totaling 138h 2m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://trust.jitterbit.com

Minor May 8, 2026

NA Harmony (East): Degraded Performance

Detected by Pingoru
May 08, 2026, 02:21 AM UTC
Resolved
May 08, 2026, 05:25 AM UTC
Duration
3h 4m
Affected: Management ConsoleHarmony PortalCloud PlatformCloud StudioProduction Cloud Agent GroupSandbox Cloud Agent GroupAPI ManagerCloud API GatewayMarketplaceRuntime Operation LogsCloud DatastoreJitterbit MQ
Timeline · 6 updates

Read the full incident report →

Major April 15, 2026

LATAM: Wevo iPaaS Degradation

Detected by Pingoru
Apr 15, 2026, 01:22 PM UTC
Resolved
Apr 15, 2026, 02:26 PM UTC
Duration
1h 4m
Affected: Cloud Database
Timeline · 4 updates
  1. investigating Apr 15, 2026, 01:22 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. identified Apr 15, 2026, 01:27 PM UTC

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

  3. monitoring Apr 15, 2026, 02:18 PM UTC

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

  4. resolved Apr 15, 2026, 02:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 9, 2026

Missing API Logs

Detected by Pingoru
Apr 09, 2026, 02:35 PM UTC
Resolved
Apr 09, 2026, 04:05 PM UTC
Duration
1h 30m
Affected: API ManagerAPI ManagerAPI Manager
Timeline · 4 updates
  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 →

Minor February 26, 2026

Harmony SAML authentication

Detected by Pingoru
Feb 26, 2026, 05:17 PM UTC
Resolved
Feb 27, 2026, 10:08 PM UTC
Duration
1d 4h
Affected: Harmony PortalHarmony PortalHarmony Portal
Timeline · 3 updates
  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 →

Minor November 14, 2025

NA eiCloud API : Degraded Performance

Detected by Pingoru
Nov 14, 2025, 03:02 PM UTC
Resolved
Nov 14, 2025, 06:03 PM UTC
Duration
3h 1m
Affected: Portal
Timeline · 3 updates
  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 →

Critical November 14, 2025

EMEA Outage

Detected by Pingoru
Nov 14, 2025, 10:21 AM UTC
Resolved
Nov 14, 2025, 11:54 AM UTC
Duration
1h 33m
Affected: Management ConsoleHarmony PortalCloud PlatformCloud StudioProduction Cloud Agent GroupSandbox Cloud Agent GroupAPI ManagerCloud API GatewayEDIMarketplaceRuntime Operation LogsCloud DatastoreJitterbit MQ
Timeline · 5 updates

Read the full incident report →

Minor November 13, 2025

eiCloud UI/API (NA Region): Degraded Performance

Detected by Pingoru
Nov 13, 2025, 06:12 PM UTC
Resolved
Nov 14, 2025, 12:19 AM UTC
Duration
6h 7m
Affected: Portal
Timeline · 6 updates
  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 →

Minor November 12, 2025

eiCloud API Gateway (NA Region): Degraded Performance

Detected by Pingoru
Nov 12, 2025, 08:56 PM UTC
Resolved
Nov 13, 2025, 12:50 AM UTC
Duration
3h 53m
Affected: PortalConnectors
Timeline · 4 updates
  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 →

Minor October 20, 2025

Harmony iPaaS: JitterbitMQ slowness in NA (North America)

Detected by Pingoru
Oct 20, 2025, 06:32 PM UTC
Resolved
Oct 20, 2025, 10:06 PM UTC
Duration
3h 33m
Affected: Cloud Platform
Timeline · 4 updates
  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 →

Minor October 20, 2025

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

Detected by Pingoru
Oct 20, 2025, 04:54 PM UTC
Resolved
Oct 20, 2025, 10:00 PM UTC
Duration
5h 5m
Affected: Flow Runtime CoreWevo iPaaS PortalOn-Premise Agent
Timeline · 7 updates
  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 →

Notice September 12, 2025

LATAM: Wevo iPaaS unresponsive for VIVO Internet Provider

Detected by Pingoru
Sep 12, 2025, 03:24 PM UTC
Resolved
Sep 12, 2025, 03:41 PM UTC
Duration
16m
Affected: Wevo iPaaS Portal
Timeline · 3 updates
  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 →

Minor August 13, 2025

LATAM: Wevo iPaaS is facing slowness during execution logs processing

Detected by Pingoru
Aug 13, 2025, 12:10 PM UTC
Resolved
Aug 13, 2025, 01:29 PM UTC
Duration
1h 19m
Affected: Runtime Flow Logs
Timeline · 4 updates
  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 →

Minor June 9, 2025

EDI degradation

Detected by Pingoru
Jun 09, 2025, 07:55 AM UTC
Resolved
Jun 09, 2025, 08:19 AM UTC
Duration
24m
Affected: Platform
Timeline · 2 updates
  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 →

Critical May 2, 2025

Wevo iPaaS is facing slowness during platform navigation and flow's execution

Detected by Pingoru
May 02, 2025, 11:36 AM UTC
Resolved
May 02, 2025, 12:49 PM UTC
Duration
1h 13m
Affected: Flow Runtime CoreWevo iPaaS Portal
Timeline · 8 updates
  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 →

Notice April 22, 2025

Harmony iPaaS has high response time

Detected by Pingoru
Apr 22, 2025, 02:30 PM UTC
Resolved
Apr 22, 2025, 02:30 PM UTC
Duration
Timeline · 2 updates
  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 →

Major April 1, 2025

[Wevo iPaaS Latam] - Partial unavailability in flow's execution

Detected by Pingoru
Apr 01, 2025, 07:30 PM UTC
Resolved
Apr 01, 2025, 10:40 PM UTC
Duration
3h 9m
Affected: Flow Runtime Core
Timeline · 5 updates
  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 →

Minor March 11, 2025

EMEA Harmony (West): Degraded Performance

Detected by Pingoru
Mar 11, 2025, 10:49 AM UTC
Resolved
Mar 11, 2025, 11:15 AM UTC
Duration
25m
Affected: Management Console
Timeline · 3 updates
  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 →

Minor December 24, 2024

Flow execution logs with slow processing

Detected by Pingoru
Dec 24, 2024, 06:22 PM UTC
Resolved
Dec 24, 2024, 09:47 PM UTC
Duration
3h 25m
Affected: Runtime Flow Logs
Timeline · 4 updates
  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 →

Minor October 18, 2024

Delay in Runtime Operation Status in EMEA

Detected by Pingoru
Oct 18, 2024, 11:41 AM UTC
Resolved
Oct 18, 2024, 12:22 PM UTC
Duration
40m
Affected: Runtime Operation Logs
Timeline · 4 updates
  1. investigating Oct 18, 2024, 11:41 AM UTC

    We are currently investigating this issue.

  2. identified Oct 18, 2024, 12:05 PM UTC

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

  3. monitoring Oct 18, 2024, 12:07 PM UTC

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

  4. resolved Oct 18, 2024, 12:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 16, 2024

[ iPaaS Latam ] - General unavailability in flows and logs

Detected by Pingoru
Oct 16, 2024, 01:27 PM UTC
Resolved
Oct 17, 2024, 01:40 AM UTC
Duration
12h 12m
Affected: Flow Runtime CoreRuntime Flow Logs
Timeline · 8 updates
  1. investigating Oct 16, 2024, 01:27 PM UTC

    Flow execution and logs unavailability

  2. investigating Oct 16, 2024, 05:01 PM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 16, 2024, 05:28 PM UTC

    We are continuing to investigate this issue.

  4. investigating Oct 16, 2024, 06:53 PM UTC

    We are continuing to investigate this issue.

  5. investigating Oct 16, 2024, 06:56 PM UTC

    We are continuing to investigate this issue.

  6. investigating Oct 16, 2024, 09:03 PM UTC

    We are continuing to investigate this issue.

  7. monitoring Oct 16, 2024, 09:04 PM UTC

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

  8. resolved Oct 17, 2024, 01:40 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 10, 2024

Missing and/or incorrect EDI segment causing transaction failures

Detected by Pingoru
Oct 10, 2024, 05:28 PM UTC
Resolved
Oct 11, 2024, 01:09 PM UTC
Duration
19h 40m
Affected: PlatformPlatformPlatform
Timeline · 2 updates
  1. monitoring Oct 10, 2024, 05:28 PM UTC

    Root cause has been identified and fixed. Ongoing efforts to identify and resubmit the affected transactions

  2. resolved Oct 11, 2024, 01:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 30, 2024

[ iPaaS Latam ] Failed to register Storage in the Dashboard from 2023-08-10 to 2023-08-23

Detected by Pingoru
Sep 30, 2024, 08:28 PM UTC
Resolved
Sep 30, 2024, 08:28 PM UTC
Duration
Timeline · 1 update
  1. resolved Sep 30, 2024, 08:28 PM UTC

    After updating the database drive in the microservices, the current date format was no longer compatible and for this reason there was a failure in recording data from the Storage. We adjusted the compatibility in the microservices and the data is stored correctly again Posted 1 year ago. Sep 01, 2023 - 17:20 GMT-03:00

Read the full incident report →