Summary

On Sunday January 24 at 2:15am ET, a server that routes requests between our co-location facility and one of our cloud regions crashed. This region is used by Yext’s Professional Services group to run ETL jobs that load data from customer systems into the Yext Knowledge Graph, and the crash resulted in jobs scheduled for Sunday morning to fail to run. On Monday morning, we noticed the issue and restored service at 10:26am ET, and we ran the jobs which had failed on Sunday. This incident delayed affected customers' data updates propagating to their Yext Knowledge Graph, but no data was lost.

Remediation

We are adding a paging-severity alert to monitor the health of this router, bringing the monitoring up to parity with the infrastructure used to serve our product.

Posted Jan 29, 2021 - 13:28 EST

Resolved

This incident has been resolved.

Posted Jan 25, 2021 - 16:34 EST

Monitoring

ETLs are continuing to run and apply updated data to affected customer accounts.

Posted Jan 25, 2021 - 12:39 EST

Identified

We have identified a connectivity problem that started over the weekend and prevented normally scheduled ETLs from running and loading updated data for customer accounts. We resolved the issue, and ETLs are currently running, but affected customers may still observe a delay until their data is updated. This only affects accounts which have contracted Yext to build data loading processes for integration with their existing systems.

Posted Jan 25, 2021 - 11:28 EST