- Detected by Pingoru
- Jun 11, 2026, 11:32 AM UTC
- Resolved
- Jun 12, 2026, 07:00 PM UTC
- Duration
- 1d 7h
Timeline · 1 update
-
resolved Jun 11, 2026, 11:32 AM UTC
We found an issue that caused our "Connect to Google/Yelp/Facebook" Optimization API tasks to not be returned from May 12, 2026 ~3:00 PM EST to June 11, 2026 7:30 AM EST. We have resolved the issue, and expect these tasks should be properly returned in the API for all customers now.
Read the full incident report →
- Detected by Pingoru
- Jun 04, 2026, 08:16 PM UTC
- Resolved
- Jun 04, 2026, 08:30 PM UTC
- Duration
- 13m
Affected: Hearsay Social
Timeline · 2 updates
-
investigating Jun 04, 2026, 08:16 PM UTC
We are aware of an issue affecting the content library that is causing errors for some users. We are investigating and will provide an update shortly.
-
resolved Jun 04, 2026, 08:30 PM UTC
We have identified and remediated the issue. We confirmed there was no impact to customers. This incident is resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2026, 08:15 PM UTC
- Resolved
- Jun 03, 2026, 10:38 PM UTC
- Duration
- 2h 23m
Affected: Analytics Queries
Timeline · 3 updates
-
investigating Jun 03, 2026, 08:15 PM UTC
We are investigating reports of reports asynchronously generated via the Analytics API being inaccessible. Our team is actively working to identify the root cause. We will update this page when we have further information.
-
monitoring Jun 03, 2026, 08:52 PM UTC
We have remediated the issue, and all new reports requested via the Analytics API should now be accessible. Clients who are encountering errors with loading previously-generated reports should make a new request to the Analytics API to regenerate their desired reports. We will continue to monitor the situation.
-
resolved Jun 03, 2026, 10:38 PM UTC
The issue affecting Analytics API has been resolved. As previously noted, all new reports requested via the Analytics API should now be accessible. Clients who are encountering errors with loading previously-generated reports should make a new request to the Analytics API to regenerate their desired reports.
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2026, 08:52 AM UTC
- Resolved
- Jun 03, 2026, 11:03 AM UTC
- Duration
- 2h 10m
Affected: Review GenerationReview ResponseReviews Portal
Timeline · 3 updates
-
investigating Jun 03, 2026, 08:52 AM UTC
We are currently experiencing degraded performance affecting parts of the Reviews Portal. Some users may encounter increased latency and intermittent errors when accessing certain functionality. Our team is actively investigating and working to mitigate the issue. We will provide additional updates as more information becomes available. Impact: Reviews Portal performance may be degraded, including intermittent errors and slower response times.
-
monitoring Jun 03, 2026, 09:43 AM UTC
We have identified and mitigated the issue that was causing degraded performance in the Reviews Portal and related functionality. System load has returned to normal levels, and service performance has stabilized. We are continuing to monitor the platform closely to ensure the recovery is sustained. Users should no longer experience the elevated latency, timeouts, or intermittent errors reported earlier.
-
resolved Jun 03, 2026, 11:03 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 02, 2026, 05:32 PM UTC
- Resolved
- Jun 03, 2026, 06:10 PM UTC
- Duration
- 1d
Affected: Managed Services ETLs
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- May 20, 2026, 12:17 PM UTC
- Resolved
- May 20, 2026, 04:37 PM UTC
- Duration
- 4h 20m
Affected: Hearsay Social
Timeline · 3 updates
-
investigating May 20, 2026, 12:17 PM UTC
We are currently investigating elevated error rates from LinkedIn APIs used by Hearsay Social to monitor LinkedIn user activity, including posts, comments, and profile updates. Customers may experience delays in LinkedIn activity capture and monitoring. We are working with LinkedIn and monitoring recovery. We will provide another update as more information becomes available.
-
monitoring May 20, 2026, 03:56 PM UTC
LinkedIn has implemented a fix and we are monitoring results.
-
resolved May 20, 2026, 04:37 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 03:07 PM UTC
- Resolved
- May 19, 2026, 04:19 PM UTC
- Duration
- 1h 11m
Affected: Hearsay Platform
Timeline · 4 updates
-
investigating May 19, 2026, 03:07 PM UTC
We are seeing degraded performance with some areas of the Hearsay application likely due to heavy traffic. We are actively investigating and will update shortly. No data loss is expected at this time
-
identified May 19, 2026, 03:59 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring May 19, 2026, 04:02 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 19, 2026, 04:19 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 13, 2026, 05:24 PM UTC
- Resolved
- May 13, 2026, 08:40 PM UTC
- Duration
- 3h 15m
Affected: Listings Portal
Timeline · 2 updates
-
monitoring May 13, 2026, 05:24 PM UTC
We have identified errors in the Listings pages within the portal. We have remediated the errors and will continue to monitor the situation.
-
resolved May 13, 2026, 08:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 12, 2026, 10:33 PM UTC
- Resolved
- May 13, 2026, 11:45 PM UTC
- Duration
- 1d 1h
Affected: Connectors Processing
Timeline · 4 updates
-
identified May 12, 2026, 10:33 PM UTC
We have identified an issue that has been causing delays in Crawler runs since 4:00 AM EST earlier today (May 12, 2026).
-
identified May 13, 2026, 06:37 AM UTC
Crawler runs are still delayed; we are continuing to work on figuring out the source of the delays.
-
monitoring May 13, 2026, 06:10 PM UTC
We have resolved the delays causing Crawler runs to be stuck over the last ~34 hours. As part of our resolution, we needed to cancel all active crawls. For customers with one-off or weekly crawl configurations, we have restarted all your crawls (and all but five weekly crawls are still in progress). For customers with daily crawl configurations, you should feel free to manually restart your crawls, or expect that they will run again at their normally scheduled time in the next 24 hours.
-
resolved May 13, 2026, 11:45 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 12, 2026, 04:09 PM UTC
- Resolved
- May 13, 2026, 04:34 PM UTC
- Duration
- 1d
Affected: Search IndexingReviews Portal
Timeline · 5 updates
-
investigating May 12, 2026, 04:09 PM UTC
Due to some underlying infrastructure issues we are working to resolve, data updates in Yext Search may be delayed and Review Language classification is down in Yext Reviews.
-
identified May 12, 2026, 06:57 PM UTC
The issue has been identified and a fix is being implemented.
-
identified May 12, 2026, 07:05 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring May 12, 2026, 08:32 PM UTC
A fix has been implemented and we are monitoring the impacted systems.
-
resolved May 13, 2026, 04:34 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 30, 2026, 11:39 PM UTC
- Resolved
- Apr 30, 2026, 09:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 30, 2026, 11:39 PM UTC
An issue with the US Customer Portal was identified and mitigated. Between 5:30pm and 6:10pm ET on 4/30/2026, the portal may have been unavailable or the navigation bar may have failed to render. The portal is now operating normally.
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2026, 01:34 PM UTC
- Resolved
- Apr 30, 2026, 01:30 PM UTC
- Duration
- 23h 56m
Affected: Pages GenerationContent Portal
Timeline · 4 updates
-
investigating Apr 29, 2026, 01:34 PM UTC
We are currently investigating reports of publishing delays for a subset of Pages sites.
-
identified Apr 29, 2026, 02:19 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Apr 29, 2026, 05:10 PM UTC
We have implemented a fix for this issue and publishing has resumed. There was also a partial impact to the Content Portal which has also been mitigated. We will continue to monitor the situation.
-
resolved Apr 30, 2026, 01:30 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 09:54 AM UTC
- Resolved
- Apr 22, 2026, 01:29 PM UTC
- Duration
- 3h 35m
Affected: Analytics Queries
Timeline · 5 updates
-
investigating Apr 22, 2026, 09:54 AM UTC
We are investigating reports of a partial outage in Analytics API
-
identified Apr 22, 2026, 10:33 AM UTC
The issue has been identified and a fix is being implemented.
-
identified Apr 22, 2026, 11:34 AM UTC
We have mitigated the issue for most affected customers. We are continuing to work on completely resolving the issue.
-
monitoring Apr 22, 2026, 12:17 PM UTC
We have remediated the issue. We will continue to monitor the situation.
-
resolved Apr 22, 2026, 01:29 PM UTC
This incident is resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 06:00 PM UTC
- Resolved
- Apr 09, 2026, 07:03 PM UTC
- Duration
- 1h 3m
Affected: Managed Services ETLs
Timeline · 2 updates
-
monitoring Apr 09, 2026, 06:00 PM UTC
A issue delaying Managed Services ETLs was identified and mitigated. Between 1:15am and 12:52pm ET on 4/9/2026, Managed Services ETLs were delayed in running. All systems are now operating normally, any delayed data updates will be processed, and our teams are monitoring. We will provide a final update by 3:00pm ET on 4/9/2026.
-
resolved Apr 09, 2026, 07:03 PM UTC
This incident is resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 08, 2026, 10:21 AM UTC
- Resolved
- Apr 08, 2026, 01:00 PM UTC
- Duration
- 2h 38m
Affected: Review Response
Timeline · 4 updates
-
investigating Apr 08, 2026, 10:21 AM UTC
We are investigating reports of delays in processing of automated and generative review responses.
-
identified Apr 08, 2026, 10:25 AM UTC
We have identified the issue and are working on remediation.
-
monitoring Apr 08, 2026, 11:10 AM UTC
We have remediated the issue, and are processing the delayed data. We will continue to monitor the situation.
-
resolved Apr 08, 2026, 01:00 PM UTC
All delayed items have been processed and are now operating in the expected timeframe for new responses. This incident is resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 03:16 PM UTC
- Resolved
- Mar 19, 2026, 10:35 PM UTC
- Duration
- 7h 18m
Affected: Hearsay Compliance
Timeline · 3 updates
-
identified Mar 19, 2026, 03:16 PM UTC
We have identified an issue with detect-in for native video posts not functioning in Supervision for some users. This does not affect video posts published from within the Hearsay platform. We are working to mitigate the problem.
-
monitoring Mar 19, 2026, 06:39 PM UTC
We have deployed a fix to detect-in for native video posts in Supervision. We will continue to monitor for any adverse effects.
-
resolved Mar 19, 2026, 10:35 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2026, 10:51 PM UTC
- Resolved
- Mar 19, 2026, 02:15 AM UTC
- Duration
- 3h 23m
Affected: Search Indexing
Timeline · 3 updates
-
identified Mar 18, 2026, 10:51 PM UTC
Due to this ongoing incident, customers may not see updates to Japanese profiles properly reflected in their Search experience.
-
monitoring Mar 18, 2026, 11:45 PM UTC
A fix has been implemented and we're monitoring search indexing.
-
resolved Mar 19, 2026, 02:15 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 05:40 PM UTC
- Resolved
- Mar 13, 2026, 02:30 PM UTC
- Duration
- 20h 50m
Affected: Hearsay Social
Timeline · 3 updates
-
identified Mar 12, 2026, 05:40 PM UTC
We are currently seeing errors from the Facebook API when attempting to publish video posts. As a result, video posts to Facebook may fail to publish. This appears to be an issue originating from Facebook’s API. We have contacted Meta and are monitoring the situation closely. Other Facebook post types (text and image) are functioning normally. We will share updates as soon as we receive additional information.
-
monitoring Mar 13, 2026, 10:38 AM UTC
The issue affecting video post publishing to Facebook has been resolved. Facebook’s API is now operating normally, and video posts are successfully publishing again. We will continue to monitor to ensure stability.
-
resolved Mar 13, 2026, 02:30 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 04, 2026, 02:18 PM UTC
- Resolved
- Mar 04, 2026, 04:15 PM UTC
- Duration
- 1h 57m
Affected: Management APIListings ScanningCustomer Portal LoginResellers Portal
Timeline · 7 updates
-
investigating Mar 04, 2026, 02:18 PM UTC
We are currently investigating this issue.
-
investigating Mar 04, 2026, 02:25 PM UTC
We are continuing to investigate this issue.
-
investigating Mar 04, 2026, 02:29 PM UTC
We are continuing to investigate this issue.
-
investigating Mar 04, 2026, 02:45 PM UTC
We have received reports from our ISP that they are experiencing an outage on our primary and backup links.
-
monitoring Mar 04, 2026, 03:21 PM UTC
Our ISP appears to have remediated the issue. We will continue to monitor the situation.
-
resolved Mar 04, 2026, 04:15 PM UTC
This incident is resolved.
-
postmortem Mar 09, 2026, 01:01 PM UTC
### Summary From approximately 9:08 EST to 10:15 EST on March 4, 2026, the US Customer Portal, Management API, and Scan API were unavailable. ### Root Cause The incident was caused by an outage of the ISP for both our primary and backup links. ### Remediation The incident was resolved when our ISP remediated the issue.
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 08:59 PM UTC
- Resolved
- Mar 03, 2026, 12:21 PM UTC
- Duration
- 15h 22m
Affected: Reviews PortalNotifications Portal
Timeline · 5 updates
-
identified Mar 02, 2026, 08:59 PM UTC
We're investigating reports of delays in sending Reviews notifications.
-
identified Mar 02, 2026, 10:45 PM UTC
We identified an issue that delayed Reviews Analytics notifications beginning February 25. We’re working to send the delayed reports as soon as possible.
-
monitoring Mar 02, 2026, 11:07 PM UTC
We’ve verified that Reviews Analytics notification emails are functioning normally again, including correct image attachments. We’re continuing to send any missed notifications and delayed reports from the impact period. We’ll continue to monitor and perform additional checks to ensure notifications and reports are delivered as expected. This issue is now mitigated.
-
monitoring Mar 03, 2026, 08:45 AM UTC
We are continuing to monitor for any further issues.
-
resolved Mar 03, 2026, 12:21 PM UTC
We’ve verified that Reviews Analytics notification emails are functioning normally again, including correct image attachments. All eligible missed notifications and delayed reports from the impact period have now been successfully sent. This applies exclusively to reports with a sending frequency greater than daily (e.g., weekly or monthly), as daily reports were not reissued. The system is fully operational, and we’ve completed additional monitoring and validation to ensure notifications and reports are being delivered as expected. This issue is fully resolved.
Read the full incident report →
Critical February 25, 2026 - Detected by Pingoru
- Feb 25, 2026, 04:09 PM UTC
- Resolved
- Feb 26, 2026, 01:20 AM UTC
- Duration
- 9h 10m
Affected: Hearsay Social
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Feb 23, 2026, 05:55 PM UTC
- Resolved
- Feb 22, 2026, 12:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Feb 23, 2026, 05:55 PM UTC
We experienced delays in publishing Classic Pages content and degraded performance in the Pages platform from approximately 7:00 PM ET on Saturday, February 21 to 12:30 AM ET on Sunday, February 22. The issue has since been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 23, 2026, 02:45 PM UTC
- Resolved
- Feb 23, 2026, 04:50 PM UTC
- Duration
- 2h 5m
Affected: Hearsay Social
Timeline · 3 updates
-
investigating Feb 23, 2026, 02:45 PM UTC
We are currently investigating this issue.
-
monitoring Feb 23, 2026, 03:27 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 23, 2026, 04:50 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 19, 2026, 05:09 PM UTC
- Resolved
- Feb 19, 2026, 07:49 PM UTC
- Duration
- 2h 40m
Affected: Pages Generation
Timeline · 4 updates
-
investigating Feb 19, 2026, 05:09 PM UTC
We are investigating reports of delays in Pages generation.
-
identified Feb 19, 2026, 05:43 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Feb 19, 2026, 06:29 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 19, 2026, 07:49 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 18, 2026, 05:00 PM UTC
- Resolved
- Feb 18, 2026, 07:24 PM UTC
- Duration
- 2h 24m
Affected: Analytics Ingestion
Timeline · 4 updates
-
investigating Feb 18, 2026, 05:00 PM UTC
We are investigating reports of delays in Analytics metrics.
-
identified Feb 18, 2026, 05:17 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Feb 18, 2026, 06:21 PM UTC
We have deployed a fix for the delayed Analytics ingestion affecting Analytics Events and associated metrics. Most users should now see related Pages and Search metrics for the affected time period in the platform, though some metrics requests may continue to be cached across the next two hours. We will continue to monitor for any adverse effects.
-
resolved Feb 18, 2026, 07:24 PM UTC
The issue affecting Analytics Events ingestion has been resolved. All systems are now operating normally. The issue began at February 16, 2026 at 6:00 AM EST and was resolved at February 18, 2026 at 1:21 PM EST. We apologize for any inconvenience this may have caused.
Read the full incident report →