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
Posted May 08, 2026 - 19:32 UTC
Resolved
The issue has been mitigated.
Posted May 08, 2026 - 05:25 UTC
Monitoring
A fix has been implemented and we are monitoring the results.
Posted May 08, 2026 - 04:06 UTC
Update
We are continuing to investigate this issue.
Posted May 08, 2026 - 03:19 UTC
Update
We are continuing to investigate this issue.
Posted May 08, 2026 - 02:56 UTC
Investigating
We are currently experiencing degraded performance in our Harmony platform in the NA (East) region. Please check back for updates.
Posted May 08, 2026 - 02:21 UTC
This incident affected: NA Harmony (Management Console, Harmony Portal, Cloud Platform, Cloud Studio, Production Cloud Agent Group, Sandbox Cloud Agent Group, API Manager, Cloud API Gateway, Marketplace, Runtime Operation Logs, Cloud Datastore, Jitterbit MQ).