Zendesk QA will undergo infrastructure migration across 15 non-consecutive days in March 2026, with affected customers experiencing up to 30 minutes of downtime per maintenance window. The migration targets multiple infrastructure pods and will be staggered across the month—beginning 4-6 March, resuming 9-13 March, and concluding 18-27 March—with each window spanning 7 AM to 3 PM UTC. Only customers who receive in-product banner notifications will be impacted, suggesting a phased rollout rather than a platform-wide outage. The stated objective is infrastructure modernisation to improve scalability and reliability, though the extended timeline and pod-based approach indicate either significant architectural complexity or a cautious deployment strategy.
For support teams relying on QA for quality assurance workflows, the implications are material but manageable. The 30-minute maximum disruption window is modest, yet the distributed nature of the maintenance—spanning nearly four weeks—creates operational friction that extends beyond individual downtime events. Teams will need to coordinate QA audits, calibration sessions, and performance reviews around these windows, particularly those operating across multiple time zones where the 7 AM-3 PM UTC window may overlap peak business hours. The staggered approach raises a practical question: are teams on later pods receiving the same feature parity and bug fixes as early-wave customers, and if so, how should this inform QA scheduling during the transition period?
The broader context matters here. As the industry shifts toward agentic AI and automated quality monitoring, infrastructure investments in QA become increasingly critical—these systems now underpin agent performance measurement for AI-assisted workflows. Zendesk's decision to modernise QA infrastructure suggests the product is handling greater data volumes and complexity than its current architecture supports. For administrators, this maintenance window is an opportunity to audit QA dependencies, test failover procedures, and communicate clearly with stakeholders about expected disruptions. The 14-day advance notification via in-product banners is standard practice, but teams should treat this as a trigger to review their QA-dependent processes rather than a passive alert.
Zendesk will perform critical maintenance which will impact Zendesk QA availability for some customers in March, 2026, during the days listed below.Affected products: Zendesk QA Important: Only Zendesk QA customers who have been notified via in-product banners will be impacted, based on the maintena
Zendesk will perform critical maintenance which will impact Zendesk QA availability for some customers in March, 2026, during the days listed below.Affected products: Zendesk QA Important: Only Zendesk QA customers who have been notified via in-product banners will be impacted, based on the maintena