Yext Status

Yext

All Systems Operational

Pages Serving Operational

Pages Generation Operational

Live API Operational

Search Serving Operational

Customer Portal Operational

Platform API (Knowledge and Administrative) Operational

Publisher Network Operational

Sandbox Operational

Knowledge Assistant Operational

Hitchhiker Site Operational

Analytics Operational

Managed Services Operational

App Directory Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Feb 8, 2023

No incidents reported today.

Feb 7, 2023

Realtime analytics outage

Resolved - This incident has been resolved.
Feb 7, 18:24 EST

Monitoring - Our analytics backend experienced a brief outage that will result in a loss of analytics data. This may have also impacted availability of listings on some publishers.

A fix has been applied and we are continuing to monitor.
Feb 7, 17:22 EST

Feb 6, 2023

No incidents reported.

Feb 5, 2023

Scheduled Maintenance

Completed - The scheduled maintenance has been completed.
Feb 5, 05:01 EST

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 5, 00:03 EST

Scheduled - A maintenance window is scheduled from 12:00am to 5:00am US Eastern Time on Sunday, February 5th. During this time, the Customer Portal and Platform API services may be unavailable. Pages Serving and Live API will be unaffected. We will provide updates as the maintenance occurs.
Jan 18, 11:40 EST

Feb 4, 2023

No incidents reported.

Feb 3, 2023

No incidents reported.

Feb 2, 2023

Issues serving Pages content

Resolved - This incident has been resolved.
Feb 2, 12:50 EST

Update - We have verified that the impact for this incident was limited to the domains for a single customer, and are working with them on follow up.
Feb 2, 12:12 EST

Monitoring - A fix has been implemented and we are monitoring the results.
Feb 2, 11:57 EST

Identified - A subset of Pages sites are currently serving empty content. The cause of the problem has been identified and we are working to remediate. There is no loss of data.
Feb 2, 10:56 EST

Feb 1, 2023

No incidents reported.

Jan 31, 2023

No incidents reported.

Jan 30, 2023

No incidents reported.

Jan 29, 2023

No incidents reported.

Jan 28, 2023

No incidents reported.

Jan 27, 2023

No incidents reported.

Jan 26, 2023

Content API Requests Not Reported as Usage

Resolved - We identified that we have not been recording requests to the Content API (formerly known as Streams API) as part of Live API Usage. The impact of this incorrect reporting is that customer usage of the Content API has not been counted towards purchased capacity; thus, customers leveraging this feature have been receiving free usage.

We are working on resolving this issue; going forward, each request to the Content API will be counted towards the purchased capacity of Live API Calls. This behavior has always been intended, and should have been reflected in contracts. We will provide an update as soon as this issue is resolved.

Note: We will not retroactively count requests to the Content API against purchased capacity. This change will only be applicable to requests going forward.
Jan 26, 17:00 EST

Jan 25, 2023

We are investigating reports of errors in Customer Portal and Platform API

Resolved - This incident is resolved.
Jan 25, 20:49 EST

Update - We are continuing to monitor for any further issues.
Jan 25, 20:48 EST

Monitoring - We have remediated the errors. We will continue to monitor the situation.
Jan 25, 14:12 EST

Identified - The issue has been identified and a fix is being implemented.
Jan 25, 09:16 EST

Investigating - We are currently investigating this issue.
Jan 25, 08:39 EST

Listings pages in the platform and api are unreliable

Resolved - This incident has been consolidated with the other active incident: https://www.yexttrust.com/incidents/nhr13pxwrkm8. Please subscribe to the other page for updates on this issue.
Jan 25, 12:50 EST

Monitoring - A fix has been implemented and we are monitoring the results.
Jan 25, 06:32 EST

Identified - The issue has been identified and a fix is being implemented.
Jan 25, 06:26 EST