20:07 UTC | 12:07 PT
Services have been restored to Pod 6. Please let us know if there are any more concerns.
An internal tool used to monitor code usage and identify unused code was rolled out onto POD 6 to a subset of requests. The rollout caused the POD 6 datastore to become overloaded, resulting in performance degradation and service unavailability. Reverting the implementation of the internal tool restored service back to normal. In order to prevent this from happening again in the future, we will be creating a dedicated datastore specifically for the internal monitoring tool and will also be rolling out the tool to a much smaller percentage of requests moving forward.
FOR MORE INFORMATION
For current system status information about your Zendesk, check out our system status page. During an incident, you can also receive status updates by following @ZendeskOps on Twitter. The summary of our post-mortem investigation is usually posted here a few days after the incident has ended. If you have additional questions about this incident, please log a ticket with us.