Jitterbit incident

NA Harmony (East): Degraded Performance

Minor Resolved View vendor source →

Jitterbit experienced a minor incident on May 8, 2026 affecting Management Console and Harmony Portal and 1 more component, lasting 3h 4m. The incident has been resolved; the full update timeline is below.

Started
May 08, 2026, 02:21 AM UTC
Resolved
May 08, 2026, 05:25 AM UTC
Duration
3h 4m
Detected by Pingoru
May 08, 2026, 02:21 AM UTC

Affected components

Management ConsoleHarmony PortalCloud PlatformCloud StudioProduction Cloud Agent GroupSandbox Cloud Agent GroupAPI ManagerCloud API GatewayMarketplaceRuntime Operation LogsCloud DatastoreJitterbit MQ

Update timeline

  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 |