Scheduled Maintenance - February 26-27, 2026 | Pods 13, 15, 19, 20, 23, 25, 26, 27, 30 | Profiles API and Events API

Zendesk will perform critical maintenance which will impact performance for customers using the Profiles and Events APIs on multiple Pods from February 26 to February 27, 2026, during the times listed below.

Affected products:

Zendesk Sunshine Platform - Custom Data - Profiles API (Profiles)

Zendesk Sunshine Platform - Custom Data - Events API (Events)

Important: Only customers who have been notified via in-product banners will be impacted, based on the Pod maintenance dates and timings below. These banners will appear for account owners and admins in Zendesk Support on February 12, 2026. If you do not receive this alert, your account will not be impacted.

Customers Affected: Zendesk Profiles API and Events API customers on all Pods will experience a maximum service disruption of 30 minutes at some time within one of the maintenance windows below.

Date

POD

Start Time

End Time

February 26, 2026

15, 20, 25, 26, 30

22:00 UTC (Feb 26) /
14:00 PT (Feb 26)

23:30 UTC (Feb 26) /
15:30 PT (Feb 26)

February 26-27, 2026

13, 19, 23, 27

23:30 UTC (Feb 26) /
15:30 PT (Feb 26)

01:00 UTC (Feb 27) /
17:00 PT (Feb 26)

Expected behavior: Profiles API and Events API will face elevated latency. As a result requests made to the API (i.e. create, read, update or delete requests) may experience delays, errors or timeouts during the maintenance window.

What do customers have to do? During these upcoming maintenance windows, you may experience delays or errors when sending requests to the impacted services. To avoid any interruptions, we recommend holding off on sending requests during this time.

If your applications are configured with built-in retry mechanisms, please make sure those settings are active. Please keep in mind that it may still take longer than usual or not work as expected while we complete the maintenance work. Once it’s done, Profiles API and Events API performance should return to normal, and retrying your requests should succeed at this point.

Why we're doing this: The Zendesk User’s Platform team is upgrading our database to strengthen security and reliability.