Zendesk will perform critical maintenance which will impact performance for notified customers on Pod 29 on May 21 - May 23, 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 May 6, 2025.
 
Customers Affected: Zendesk Messaging and Sunshine Conversations customers on Pod 29 who have been notified, will experience a service disruption of 40 minutes during the window. Each account will only be impacted by one window, and the specific time is included in a banner alert in the Support product. If you do not receive this alert, you are not impacted.
 
Date POD Start Time End Time
May 21, 2025 29 13:30 UTC / 9:30 EST   14:10 UTC / 10:10 EST
May 21, 2025 29 14:45 UTC / 10:45 EST   15:25 UTC / 11:25 EST
May 21, 2025 29 17:15 UTC /13:15 EST   17:55 UTC / 13:55 EST
May 21, 2025 29 18:30 UTC / 14:30 EST   19:10 UTC / 15:10 EST
May 21, 2025 29 19:45 UTC / 15:45 EST   20:25 UTC / 16:25 EST
May 22, 2025 29 13:30 UTC / 9:30 EST   14:10 UTC / 10:10 EST
May 22, 2025 29 14:45 UTC / 10:45 EST   15:25 UTC / 11:25 EST
May 22, 2025 29 17:15 UTC /13:15 EST   17:55 UTC / 13:55 EST
May 22, 2025 29 18:30 UTC / 14:30 EST   19:10 UTC / 15:10 EST
May 22, 2025 29 19:45 UTC / 15:45 EST   20:25 UTC / 16:25 EST
May 23, 2025 29 13:30 UTC / 9:30 EST   14:10 UTC / 10:10 EST
May 23, 2025 29 14:45 UTC / 10:45 EST   15:25 UTC / 11:25 EST

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.

Powered by Zendesk