Hearsay Platform Errors

Incident Report for Yext

Postmortem

Summary

On July 16, 2026, users were unable to access Yext via my.hearsaysocial.com. The disruption began at 8:43 AM ET and was resolved at 9:56 AM ET, resulting in a total impact duration of approximately 73 minutes. APIs and automated integrations were not affected, and no customer data was lost or at risk.

Root Cause

An infrastructure change caused the authentication service to be unable to access the configuration it needed to function, preventing user logins. Because many platform features depend on the authentication service, this failure propagated beyond login itself and caused errors across most of the application. 

Remediation

Our team identified the cause of the incident and restored service by reverting the infrastructure change. Service was fully restored at 9:56 AM ET. A permanent fix has since been implemented, and no temporary workarounds remain in place.

To prevent recurrence, we are (1) improving our pre-production validation of infrastructure changes to confirm required configuration is in place before deployment, (2) updating the authentication service to degrade gracefully rather than fail completely when configuration is unavailable, and (3) strengthening our rapid-rollback process and exercising it on a regular basis.

Posted Jul 21, 2026 - 15:14 EDT

Resolved

This incident has been resolved.
Posted Jul 16, 2026 - 11:05 EDT

Monitoring

A fix has been implemented and we are monitoring the results.
Posted Jul 16, 2026 - 10:04 EDT

Update

We are continuing to implement the fix and will provide another update as soon as more information is available.
Posted Jul 16, 2026 - 09:52 EDT

Identified

The issue has been identified and a fix is being implemented.
Posted Jul 16, 2026 - 09:10 EDT

Investigating

We are investigating reports of errors in Hearsay Platform.
Posted Jul 16, 2026 - 09:08 EDT
This incident affected: Hearsay (Hearsay Platform).