Google Related APIs Performance Degradation
minor- Started
- Jul 3, 11:43 AM EDT
- Resolved
- Jul 12, 8:00 AM EDT
- Duration
- 212h 17m
SerpApi's updates (8)
- investigating · Jul 3, 11:43 AM EDT
We're seeing higher than normal response times on several, but not all, Google related APIs. https://github.com/serpapi/public-roadmap/issues/3972
- investigating · Jul 3, 11:44 AM EDT
We are continuing to investigate this issue.
- monitoring · Jul 4, 4:21 AM EDT
We're seeing improved response time and stability for the past couple of hours. We'll continue monitoring the performance.
- investigating · Jul 5, 2:13 PM EDT
We're seeing increased response times across several Google-related APIs since the last hour. We're investigating
- monitoring · Jul 5, 3:31 PM EDT
Good news! We deployed a fix, and we're seeing recovery. Our engineering team is continuing to monitor the situation closely and make adjustments to fully restore normal performance. We appreciate your patience and will keep you updated as we have more information. Thank you for your understanding.
- identified · Jul 6, 12:57 PM EDT
We're seeing another increase in response times this morning, most noticibly affecting our Google Shopping API. We're investigating and will follow up with any updates. Thank you for your continued patience.
- investigating · Jul 6, 12:58 PM EDT
We are currently investigating this issue.
- resolved · Jul 12, 8:00 AM EDT
We've made some internal adjustments and have seen much better performance for the past few days. We'll continue monitoring the situation. We consider this issue resolved.
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 78 ms, against 106 ms over the 24 hours before. SerpApi posted the incident at Jul 3, 11:43 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 ↗