Performance Degradation
critical- Started
- Sep 10, 11:59 AM EDT
- Resolved
- Sep 17, 6:40 PM EDT
- Duration
- 174h 40m
SerpApi's updates (16)
- investigating · Sep 10, 11:59 AM EDT
We currently experience service outage across all of our APIs. https://github.com/serpapi/public-roadmap/issues/4265
- investigating · Sep 10, 12:10 PM EDT
The team has deployed a temporary fix to mitigate the severity of the issue. We continue working on a long-term fix.
- investigating · Sep 10, 2:37 PM EDT
We are continuing to investigate this issue.
- identified · Sep 10, 2:55 PM EDT
The issue is due to recent changes on Google's side, which are causing searches to fail or time out. Our engineers have deployed a partial mitigation that is currently restoring a portion of traffic, and continue testing additional fixes to fully resolve the issue.
- monitoring · Sep 11, 12:57 PM EDT
We have made several improvements - success rates and response times should be recovering. Note that there is one remaining known issue that we are still working to resolve - the location and uule parameters are not currently reliable for locations outside the US. We have implemented a fix and are testing it now. Until it goes live, please use the gl, hl, and google_domain parameters to specify non-US locations. We’ll continue monitoring performance to ensure stability. Please don't hesitate to reach out if you have any questions or experience any further issues.
- monitoring · Sep 11, 2:59 PM EDT
We are continuing to monitor for any further issues.
- monitoring · Sep 11, 7:29 PM EDT
We are continuing to monitor for any further issues.
- investigating · Sep 14, 6:21 AM EDT
We are experiencing higher error rates and response times again. We're actively working on the issue with the highest urgency.
- identified · Sep 14, 8:09 PM EDT
We've made several improvements, and are seeing signs of recovery on several of the affected APIs. We're continuing to work on further improvements to ensure stability for Google engines.
- investigating · Sep 15, 4:34 AM EDT
We see another performance degradation. The team is investigating and working on remediation.
- investigating · Sep 16, 1:13 AM EDT
We're seeing a good trend in the success rate and response time for the last few hours. We'll keep working and monitoring the status.
- investigating · Sep 16, 2:21 PM EDT
We are still working on improvements to restore stable performance across engines. While we're noticing recovery on many engines, we're working to ensure success rates and response times continue improving. We'll continue to provide updates as the situation progresses. Thank you again for your patience.
- monitoring · Sep 17, 6:55 AM EDT
We're seeing much better, more stable overall performance over the past few hours. A few of our engines are still affected, and we're working to restore good performance across the board.
- monitoring · Sep 17, 12:38 PM EDT
You may have noticed another increase in response times since the most recent update. This was related to an improvement we attempted. That change has since been reverted until it can be further fine-tuned. Success rates and response times are recovering. We'll follow up with further updates soon, thanks again for your patience.
- monitoring · Sep 17, 2:43 PM EDT
Performance has improved significantly for several engines, while others continue to experience degradation. We'll continue monitoring, and working to restore functionality to affected APIs.
- resolved · Sep 17, 6:40 PM EDT
Performance has remained stable for many of the APIs initially affected by this issue. For updates on engines that are still experiencing degradation, you can check the relevant Public Roadmap issue: [Google Shopping API] Performance Degradation [Google News API] Performance Degradation [Google Ads API] Performance Degradation [Google Jobs API] Degraded Performance [Google Local API] Performance Degradation [Google Scholar API] Elevated Response Times [Google Forums API] Performance Degradation Alternatively, up to date information about any ongoing incidents can be found here: https://status.serpapi.com/ Thanks again for your patience.
What our checks recorded
We checked SerpApi 575 times from SerpApi's start time to its resolution, once every five minutes. Every one of them reached SerpApi's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 127 ms, against 166 ms over the 24 hours before. SerpApi posted the incident at Sep 10, 11:59 AM EDT.
Updates are SerpApi's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗