Performance degradation across many Google APIs
major- Started
- Sep 4, 5:27 PM EDT
- Resolved
- Sep 10, 2:35 PM EDT
- Duration
- 141h 8m
SerpApi's updates (5)
- investigating · Sep 4, 5:27 PM EDT
We apologize for the impact. We're currently seeing elevated response times and error rates across many Google APIs including Google Light Search API, Google Shopping API, Google News Light API, Google Jobs API and others. Related issue on our Public Roadmap: https://github.com/serpapi/public-roadmap/issues/4240
- identified · Sep 4, 8:17 PM EDT
We’ve identified the likely cause and are actively testing several potential fixes. We appreciate your patience and will share another update as soon as we have more information.
- monitoring · Sep 6, 1:40 PM EDT
Quick update: We've deployed a fix for this. We're actively monitoring the performance. Thank you for your patience while we work on this.
- investigating · Sep 8, 11:58 AM EDT
We're currently seeing elevated response times across Google APIs, including Google Search API, Google Shopping API, Google News Light API, Google Jobs API, and others. Related issue on our Public Roadmap: https://github.com/serpapi/public-roadmap/issues/4240
- resolved · Sep 10, 2:35 PM EDT
We will be closing this issue, as we have opened more specific incidents with additional information: - Google News Result Timeouts: https://status.serpapi.com/incidents/6chb6clhbgw4 - Advanced Search Operator Timeouts: https://status.serpapi.com/incidents/pts4x92phsq8 Thank you for your patience while we work to resolve these outstanding issues.
What our checks recorded
We checked SerpApi 576 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 221 ms, against 213 ms over the 24 hours before. SerpApi posted the incident at Sep 4, 5:27 PM EDT.
Updates are SerpApi's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗