All Systems Operational

Uptime over the past 90 days. View historical uptime.
Website Operational
India Cluster [AWS] Operational
Gateway Operational
Workflow Operational
Webhooks Operational
APIM Gateway Operational
Polling Operational
Job History Operational
Databases by Quickwork Operational
Embedded Journeys Operational
Content Template Operational
Job Processor - Default Operational
Job Processor - Tier 1 Operational
Job Processor - Tier 2 Operational
Job Processor - Tier 3 Operational
Japan Cluster [AWS] Operational
Gateway Operational
Workflow Operational
Webhooks Operational
Germany Cluster [Open Telekom Cloud] Operational
Gateway Operational
Workflow Operational
Webhooks Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Oct 9, 2026

No incidents reported today.

Oct 8, 2026

No incidents reported.

Oct 7, 2026

No incidents reported.

Oct 6, 2026

[Mumbai] Scheduler Performance Degradation
Resolved -

Incident:
We experienced degraded performance in the Scheduler service starting at approximately 1:32 PM.

Impact:
Some jobs using the Scheduler as a trigger or a Delay as a step experienced processing delays during the affected period. Scheduling was not completely stopped, and jobs continued to be processed, although at reduced performance. Journeys that did not rely on the Scheduler were not impacted and continued to execute successfully as usual.

Root Cause:
A sudden increase in delay and scheduler jobs resulted in a higher number of items being locked concurrently than the Scheduler could efficiently handle. This increased database lock contention and caused the Scheduler to process jobs more slowly.

Detection & Investigation:
The issue did not initially present through the usual error signals. There were no significant service-level errors or query timeouts, and MongoDB currentOp did not show any long-running queries that would indicate an immediate database performance issue. The Scheduler continued processing jobs, although at reduced performance, so there was no obvious error condition indicating the underlying database lock contention. The issue was identified by correlating the increase in job processing delays with the number of concurrently locked items.

Resolution:
We identified the underlying issue and applied a fix to control the number of concurrently locked items. Scheduler performance returned to normal at approximately 5:12 PM. Previously delayed jobs were subsequently processed successfully.

We have also implemented the necessary controls to better handle sudden increases in Scheduler workload and avoid similar performance degradation in the future.
Oct 6, 08:02 UTC

Oct 5, 2026

No incidents reported.

Oct 4, 2026

No incidents reported.

Oct 3, 2026

No incidents reported.

Oct 2, 2026

No incidents reported.

Oct 1, 2026

No incidents reported.

Sep 30, 2026

No incidents reported.

Sep 29, 2026

No incidents reported.

Sep 28, 2026

No incidents reported.

Sep 27, 2026

No incidents reported.

Sep 26, 2026

No incidents reported.

Sep 25, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage