Zendesk will perform critical maintenance which will impact performance for notified customers on Pod 27 on June 17-20 2025, during the times listed below.

Affected products: Messaging & Sunshine Conversations

Important:  Only customers with who have been notified and have Messaging enabled will be impacted, based on the Pod maintenance dates and timings below. Impacted customers will receive a notification banner in their Support product on June 1.
Customers Affected: Zendesk Messaging and Sunshine Conversations customers on Pod 27 who have been notified, will experience a service disruption of 40 minutes at some time within the 40 minute maintenance window.
Date POD Start Time End Time
June 17, 2025 27 13:30 UTC / 9:30 EDT   14:10 UTC / 10:10 EDT
June 17, 2025 27 14:45 UTC / 10:45 EDT   15:25 UTC / 11:25 EDT
June 17, 2025 27 16:00 UTC / 12:00 EDT   16:40 UTC / 12:40 EDT
June 17, 2025 27 17:15 UTC / 13:15 EDT   17:55 UTC / 13:55 EDT
June 17, 2025 27 18:30 UTC / 14:30 EDT   19:10 UTC / 15:10 EDT
June 17, 2025 27 19:45 UTC / 15:45 EDT   20:25 UTC / 16:25 EDT
June 18, 2025 27 13:30 UTC / 9:30 EDT   14:10 UTC / 10:10 EDT
June 18, 2025 27 14:45 UTC / 10:45 EDT   15:25 UTC / 11:25 EDT
June 18, 2025 27 16:00 UTC / 12:00 EDT   16:40 UTC / 12:40 EDT
June 18, 2025 27 17:15 UTC / 13:15 EDT   17:55 UTC / 13:55 EDT
June 18, 2025 27 18:30 UTC / 14:30 EDT   19:10 UTC / 15:10 EDT
June 18, 2025 27 19:45 UTC / 15:45 EDT   20:25 UTC / 16:25 EDT
June 19, 2025 27 13:30 UTC / 9:30 EDT   14:10 UTC / 10:10 EDT
June 19, 2025 27 14:45 UTC / 10:45 EDT   15:25 UTC / 11:25 EDT
June 19, 2025 27 17:15 UTC / 13:15 EDT   17:55 UTC / 13:55 EDT
June 19, 2025 27 18:30 UTC / 14:30 EDT   19:10 UTC / 15:10 EDT
June 19, 2025 27 19:45 UTC / 15:45 EDT   20:25 UTC / 16:25 EDT
June 20, 2025 27 13:30 UTC / 9:30 EDT   14:10 UTC / 10:10 EDT
June 20, 2025 27 14:45 UTC / 10:45 EDT   15:25 UTC / 11:25 EDT
June 20, 2025 27 17:15 UTC / 13:15 EDT   17:55 UTC / 13:55 EDT
June 20, 2025 27 18:30 UTC / 14:30 EDT   19:10 UTC / 15:10 EDT

Expected behavior: During the maintenance window, notified accounts attempting to use Messaging will be locked and unable to send outbound messages; instead, they 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 enabled their own client-side Content Security Policy, 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 increased reliability, performance, and data locality.

 

Powered by Zendesk