Zendesk will perform critical maintenance which will impact performance for notified customers on Pods 23 and 13 on April 29 - May 1 2025, during the times listed below.

Affected products: Messaging & Sunshine Conversations

Important: Only customers who have been notified and have Messaging enabled will be impacted, based on the Pod maintenance dates and timings below. Impacted customers will receive an in-product banner notification on April 15.

Customers Affected: Zendesk Messaging and Sunshine Conversations customers on Pods 23 and 13 who have been notified, will experience a brief service disruption of 20 minutes at some time within the 30 minute maintenance window.

Date	POD	Start Time	End Time
April 29, 2025	23, 13	13:30 UTC / 09:30 EDT	14:00 UTC / 10:00 EDT
April 29, 2025	23, 13	15:00 UTC / 11:00 EDT	15:30 UTC / 11:30 EDT
April 29, 2025	23, 13	17:30 UTC / 13:30 EDT	18:00 UTC / 14:00 EDT
April 29, 2025	23, 13	19:00 UTC / 15:00 EDT	19:30 UTC / 15:30 EDT
April 30, 2025	23, 13	13:30 UTC / 09:30 EDT	14:00 UTC / 10:00 EDT
April 30, 2025	23, 13	15:00 UTC / 11:00 EDT	15:30 UTC / 11:30 EDT
April 30, 2025	23, 13	17:30 UTC / 13:30 EDT	18:00 UTC / 14:00 EDT
April 30, 2025	23, 13	18:00 UTC / 14:00 EDT	18:30 UTC / 14:30 EDT
May 1, 2025	23, 13	13:30 UTC / 09:30 EDT	14:00 UTC / 10:00 EDT
May 1, 2025	23, 13	18:00 UTC / 14:00 EDT	18:30 UTC / 14:30 EDT
May 1, 2025	23, 13	13:30 UTC / 09:30 EDT	14:00 UTC / 10:00 EDT
May 1, 2025	23, 13	18:00 UTC / 14:00 EDT	18:30 UTC / 14:30 EDT

Expected behavior: During the maintenance window, notified accounts attempting to use Messaging will find their accounts locked and unable to send outbound messages and instead will receive an HTTP 423 response. Messages sent by end-users via social messaging channels for these accounts will be preserved and buffered until the account is unlocked.

What do customers have to do? If customers have have enabled their own client-side Content Security Policy than they must include *.zendesk.com on their allowlist to ensure that their integrations continue to initialize and function.

Why we're doing this: The Zendesk Messaging team is rehoming customers accounts to be located in the same data store as their Support accounts for increased reliability, performance & data locality.