Major incident

Yext: Elevated Rate of Errors

Affected: Pages Serving, Search Serving, Analytics Ingestion

Current status of Yext: Operational — live Yext status

Timeline

1. Oct 27, 2026, 20:29 UTC
   monitoring
   We experienced elevated errors affecting Analytics, Search, Pages, Live API, and Streams API services hosted in our EU environment. During this disruption, users may have encountered errors loading pages, retrieving search results, or making API requests. Traffic has been restored to the affected infrastructure, and services are recovering. Our team is monitoring to confirm continued stability. We will provide another update once the incident is fully resolved.
2. Oct 27, 2026, 21:54 UTC
   resolved
   On October 27, 2026, from approximately 4:00 p.m. to 4:20 p.m. EDT (20:00–20:20 UTC), services hosted in our EU environment experienced elevated errors affecting Search, Pages, Live API, Streams API, and Analytics event collection. Users may have encountered errors loading pages, retrieving search results, or making API requests. Some analytics pixel events were not collected during the disruption. Traffic was restored to the affected infrastructure, and subsequent monitoring confirmed stable operation. We apologize for the disruption. We will share a post-incident review with additional details about the cause, impact, and steps we are taking to reduce the risk of recurrence.
3. Nov 3, 2026, 15:44 UTC
   postmortem
   On October 27, 2026, between approximately 19:55 and 20:20 UTC, we experienced elevated errors affecting Search, Pages, Live API, Streams API, and Analytics services hosted in our EU environment. During this period, users may have encountered errors loading pages, retrieving search results, or making API requests. Analytics event collection was also interrupted, resulting in the loss of approximately 22 minutes of analytics pixel events. Most Pages requests continued to be served from our CDN cache. **Cause and resolution** The disruption occurred during maintenance on application servers in our EU infrastructure. The maintenance process did not reconnect servers to the public load balancers in the intended sequence. Maintenance also overlapped across two EU serving locations, interrupting traffic to the affected services. Traffic was restored as the servers reconnected to the load balancers, and services recovered. We continued monitoring to confirm stability before closing the incident at approximately 21:53 UTC. **Prevention** We have merged fixes to the maintenance automation to: * Prevent simultaneous maintenance across the affected EU serving locations. * Ensure servers reconnect to the public load balancers in the intended sequence. We apologize for the disruption and the resulting gaps in analytics reporting.

Updates as published by Yext (original).