Zendesk will perform critical maintenance which will impact performance for some accounts on Pod 25 from March 24-26 2026, during the times listed below.
Affected products: Messaging & Sunshine Conversations
Customers Affected: Zendesk Messaging and Sunshine Conversations customers who have been notified by an In-Product Message, will experience a brief service disruption of 20 minutes at some time within the 2 hour maintenance window.
| Date | POD | Start Time | End Time |
| March 24, 2026 | 25 |
18:00 UTC / 14:00 EDT |
20:00 UTC / 16:00 EDT |
| March 25, 2026 | 25 |
18:00 UTC / 14:00 EDT |
20:00 UTC / 16:00 EDT |
| March 26, 2026 | 25 |
18:00 UTC / 14:00 EDT |
20:00 UTC / 16:00 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. For end-users attempting using the Web Widget, if the widget wasn't loaded prior to the downtime the widget will not load so they won't be able to send incoming messages. If they try to send an inbound message via the widget because it was loaded prior to the maintenance they will see an error message that the message hasn't been able to be sent and they'll be able to resend once the maintenance is over. For end users using the Mobile SDKs, they will see an error when attempting to send a message and will be able to resend once the maintenance is over.
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. We also suggest that customers use https://{subdomain}.zendsk.com/sc in place of api.smooch.io
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 & data locality.