Is Yext down?
Last checked 4m agoNo incidents right now.
Yext is operational right now. Last checked 4m ago; the most recent incident resolved 15d ago.
Real-time Yext status, recent outages, and incident history — pulled directly from Yext's official status page at https://www.yexttrust.com every 5 minutes. Pingoru tracks 58 Yext services and has captured 24 incidents in the last 90 days (99.35% uptime). Get email, Slack, Discord, or webhook alerts the moment Yext reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days-
Timeline · 1 update
- resolved · Sep 16, 2026, 08:53 PM UTC
From September 9 at approximately 12:10 p.m. EDT through September 16 at 10:13 a.m. EDT, some customers may have received autocomplete suggestions that did not correspond to their submitted queries. A cache configuration issue caused query parameters, including the search input and search experience, to be omitted from the cache key for a legacy Search API endpoint. Consequently, an autocomplete response cached for one request could be returned for a different query or Search experience. The issue was limited to autocomplete requests from older frontend implementations using the legacy endpoint. Standard autocomplete requests using current endpoints were not affected, and our investigation found no evidence of meaningful customer-facing impact to search results. We corrected the cache configuration at 10:13 a.m. EDT on September 16 and verified the expected behavior within minutes. We are evaluating additional monitoring and configuration validation to help detect and prevent similar issues.
Latest: From September 9 at approximately 12:10 p.m. EDT through September 16 at 10:13 a.m. EDT, some customers may have received autocomplete suggestions that did not correspond to their …
-
- Hearsay Relate
Timeline · 3 updates
- identified · Sep 03, 2026, 04:26 PM UTC
We are currently investigating an issue affecting inbound voice services for a subset of users. Impacted users may experience issues receiving inbound calls. Our engineering team is actively investigating the cause and working to restore normal service as quickly as possible. Outbound voice services are not currently known to be affected. We will provide another update as more information becomes available.
- monitoring · Sep 03, 2026, 04:55 PM UTC
A fix has been deployed to address the inbound voice issue affecting a subset of users.
- resolved · Sep 03, 2026, 05:41 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Hearsay Platform
Timeline · 4 updates
- investigating · Sep 02, 2026, 03:09 PM UTC
We are seeing degraded performance with some areas of the Hearsay application. We are actively investigating and will update shortly.
- investigating · Sep 02, 2026, 03:21 PM UTC
We are continuing to investigate this issue.
- identified · Sep 02, 2026, 03:40 PM UTC
The issue has been identified and a fix is being implemented.
- resolved · Sep 02, 2026, 05:44 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Hearsay Platform
Timeline · 5 updates
- investigating · Aug 17, 2026, 03:36 PM UTC
We are currently investigating this issue.
- identified · Aug 17, 2026, 03:48 PM UTC
We have identified the source of errors and are working on remediation.
- monitoring · Aug 17, 2026, 04:09 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Aug 17, 2026, 05:18 PM UTC
This incident has been resolved.
- postmortem · Aug 26, 2026, 06:01 PM UTC
# Summary On August 17, 2026, users were temporarily unable to access Yext through [my.hearsaysocial.com](http://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. # Root Cause 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](http://my.hearsaysocial.com). # Remediation 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.
Latest: # Summary On August 17, 2026, users were temporarily unable to access Yext through [my.hearsaysocial.com](http://my.hearsaysocial.com) for approximately 12 minutes, from 11:20 AM t…
-
- Pages GenerationPages Portal
Timeline · 3 updates
- identified · Aug 17, 2026, 02:32 PM UTC
We have identified an ongoing GitHub service incident that is causing delays for some Yext Pages publishes and resulting in degradations in the platform. Publishing requests may take longer than expected to complete. We are monitoring GitHub’s recovery and will provide an update as more information becomes available.
- monitoring · Aug 17, 2026, 05:06 PM UTC
Github has mitigated the issues affecting Pages publishing and the portal. Service has been fully restored. We will continue to monitor the situation.
- resolved · Aug 17, 2026, 09:37 PM UTC
This incident is resolved.
Latest: This incident is resolved.
-
See the full Yext outage history
16 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Yext outage history →Or sign up free to get alerts when Yext breaks · 10 free monitors · No credit card
- Started Sep 16, 2026, 08:53 PM UTC · Resolved Sep 09, 2026, 04:00 PM UTC · —
- Inbound Voice Service Degradation ResolvedStarted Sep 03, 2026, 04:26 PM UTC · Resolved Sep 03, 2026, 05:41 PM UTC · 1h 14m
- Started Sep 02, 2026, 03:09 PM UTC · Resolved Sep 02, 2026, 05:44 PM UTC · 2h 35m
- Started Aug 17, 2026, 03:36 PM UTC · Resolved Aug 17, 2026, 05:18 PM UTC · 1h 42m
- Pages Publishing Delays ResolvedStarted Aug 17, 2026, 02:32 PM UTC · Resolved Aug 17, 2026, 09:37 PM UTC · 7h 4m
- EU Pages Publishing Delays ResolvedStarted Aug 13, 2026, 08:46 AM UTC · Resolved Aug 13, 2026, 01:45 PM UTC · 4h 59m
- Started Aug 10, 2026, 10:30 AM UTC · Resolved Aug 10, 2026, 10:30 AM UTC · —
- Started Jul 28, 2026, 09:40 PM UTC · Resolved Jul 29, 2026, 09:11 PM UTC · 23h 30m