00:09 UTC | 17:09 PT
We are happy to announce services have been restored to Pod 14
23:52 UTC | 16:52 PT
We are continuing to see improvements on POD 14. We will continue monitor.
23:06 UTC | 16:06 PT
We've identified the cause of the degradation on POD 14 and performance is starting to recover. We will continue monitor.
22:51 UTC | 15:51 PT
We're still investigating performance degradation including 500 errors and email/ticket creation delays on Pod14.
22:25 UTC | 15:25 PT
We are investigating reports of performance issues for Pod14 customers. More info as available
Pod 14 is an AWS hosted Pod. During this incident, customers experienced performance degradation including 500 errors and email/ticket creation delays with Support. AWS had a power failure that caused issues with the database. Our operations team cutover the database to a different availability zone within that region which resulted in recovery and resolution of the issue. In order to prevent another service degradation, we will be working with AWS to improve SLAs and faster failover.
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.