Inbound Voice Service Degradation
Last updateresolvedSep 3 · 17:41 UTC
This incident has been resolved.
Reported by Yext on their status page.

checked Sep 14, 2026 11:11 AM UTC · Yext's official status page
Yext is up and running.
All components operational
Statusfield watches Yext alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
Email only. No password. Free.
4 reports published by Yext in the last 30 days
When Yext breaks, it is typically resolved in 5h 4m — median across 12 resolved incidents over 90 days.
resolvedSep 3 · 17:41 UTC
This incident has been resolved.
Reported by Yext on their status page.
resolvedSep 2 · 17:44 UTC
This incident has been resolved.
Reported by Yext on their status page.
postmortemAug 26 · 18:01 UTC
On August 17, 2026, users were temporarily unable to access Yext through my.hearsaysocial.com for approximately 12 minutes, from 11:20 AM to 11:32 AM ET. No customer data was lost, and this was not a security incident.
A content library indexing process generated higher-than-expected system demand, temporarily causing service requests to fail and affecting access to Yext through my.hearsaysocial.com.
We increased system capacity to complete the rebuild and restore normal service. To prevent recurrence, we are updating the indexing process to apply smaller, incremental changes rather than requiring a full rebuild. We are also making database performance improvements to support more reliable processing during these updates.
Reported by Yext on their status page.
resolvedAug 17 · 21:37 UTC
This incident is resolved.
Reported by Yext on their status page.