Zendesk will execute a phased database upgrade across all regional pods between October 13 and 20, 2026, migrating Aurora MySQL clusters to maintain security and AWS compatibility. The maintenance spans six-hour windows distributed across four separate dates, with different pod cohorts affected on each date to minimise simultaneous impact. Whilst a full platform outage is not expected, the upgrade will create feature-specific disruptions in Advanced Action Flows, Analytics, Chat, Contact Center, Sales, Support, and Sunshine Conversations—affecting critical operational components including omnichannel routing, messaging ticket creation, AI-assisted features (Auto Assist, Intelligent Triage, Enhance Writing for Agents), and live metrics. The expected customer-visible interruption during final database switchover ranges from 5 to 20 seconds per affected service, though requests in progress may fail and require retry, and background processing may experience delays.
For CX teams, the implications are material but manageable if planned correctly. Organisations relying heavily on AI-assisted features should anticipate temporary unavailability of Auto Assist and Intelligent Triage during their assigned maintenance window—a consideration particularly relevant given the industry's current trajectory toward agentic AI systems. Teams managing high-volume messaging operations face the most exposure, as messaging ticket creation, message brokering, and routing will be temporarily degraded; contact centres operating across multiple time zones should map their pod assignments against peak traffic periods to determine whether the scheduled windows align with their busiest hours. The phased approach mitigates risk compared to a single global maintenance event, but organisations should still establish clear retry protocols and brief agents on expected behaviour, particularly around failed requests and delayed notifications. The critical question for larger deployments is whether the six-hour window—even with only 5–20 seconds of visible downtime—creates unacceptable SLA risk during customer-critical periods, and whether advance communication to high-touch accounts is warranted.
The upgrade reflects Zendesk's infrastructure maturation rather than a reactive fix, positioning the platform for continued AWS support and long-term stability. However, the breadth of affected features underscores the centralised dependency on Aurora for core CX operations, meaning any unexpected complications during switchover could cascade across multiple product lines simultaneously. Teams should confirm their pod assignment now, document which features their workflows depend on, and establish monitoring protocols for the relevant maintenance window to catch any post-switchover anomalies that persist beyond the expected recovery period.
Zendesk will perform scheduled database maintenance between October 13 and Oct 20, 2026 as part of a critical version upgrade to the “AWS Aurora” software. This will affect database clusters in all Zendesk regions and Advanced Action Flows, Analytics, Chat, Contact Center, Sales, Support, and Sunshi