SerpApi

Affected: Search API

1. investigating 2026-10-21 10:02 UTC

   We are currently investigating the issue with Google Search APIs for empty results due to paginated queries. Our team is actively looking into this, and we will share another update once we have more information. You can track the progress of this issue on our public roadmap:...

2. investigating 2026-10-21 10:02 UTC

   We are continuing to investigate this issue.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Lens API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-16 19:52 UTC

   We’re currently seeing elevated response times and a decrease in success rates for Google Lens API. Our engineering team is investigating and working to restore normal performance. We are tracking this issue on our Public Roadmap here:...

2. identified 2026-10-19 10:36 UTC

   Our engineering team has identified the issue and are is currently working towards a fix. Thank you for your patience in the meantime.

3. identified 2026-10-19 19:59 UTC

   We’ve released several fixes and are seeing improved response times and lower error rates for the Google Lens API. Our engineering team continues working to restore expected performance.

4. monitoring 2026-10-21 10:11 UTC

   A robust fix has been implemented and we've been monitoring since the last 14 hours.

5. resolved 2026-10-21 11:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Search API

1. investigating 2026-10-14 05:42 UTC

   We are currently investigating an issue where searches using advanced operators on the Bing Search API are returning empty results. Our team is actively looking into this, and we will share another update once we have more information. You can track the progress of this issue on...

2. identified 2026-10-19 10:42 UTC

   Our engineers are currently exploring and working on different solutions which have shown good early response for this issue. We'll keep updating any improvements here.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Search API, Shopping API

1. investigating 2026-10-13 15:09 UTC

   We've been observing Google returning irrelevant/poisoned results for the past few weeks. It appears to have escalated recently. The team is looking into it urgently and working on potential fixes. https://github.com/serpapi/public-roadmap/issues/3781

2. investigating 2026-10-14 13:53 UTC

   Our engineering team has deployed an update that should reduce the number of instances in which poisoned results are returned instead of valid output. We're still working on fully addressing the issue. Thank you for understanding.

3. investigating 2026-10-19 22:38 UTC

   Google Shopping API is also now affected by this issue, you can see the related issue here: https://github.com/serpapi/public-roadmap/issues/4475 We’ll continue working on a complete solution for all APIs and will provide further updates as more information becomes available....

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Brave AI Mode API

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-13 08:26 UTC

   Brave AI Mode API has been fully down since Saturday 10/10. The team is investigating the issue.

2. resolved 2026-10-13 10:36 UTC

   We deployed a fix and the API is back up.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Search API, Search API, Images Light API, News Light API, AI Overview API, Shopping Light API, Videos Light API, Images API, Immersive Product API, Jobs API, Lens API, Local API, News API, Shopping API, Videos API

1. investigating 2026-10-06 15:51 UTC

   We are currently experiencing a partial service outage affecting multiple APIs. Our engineering team is actively investigating the issue and working to restore normal service as soon as possible. We apologize for the disruption and will provide updates as we make progress:...

2. identified 2026-10-07 13:02 UTC

   While performance is better than when the issue was reported, we're still experiencing significant degradation across many Google services, including Google Search, Google Ads, Google Images Light, Google Jobs, Google Light, Google News Light, and Google Shopping APIs. The team...

3. identified 2026-10-07 18:41 UTC

   We're continuing to experience significant performance degradation across many of our Google based APIs. We have implemented a potential solution, which is currently in review. Thank you again for your patience while we work to resolve this.

4. identified 2026-10-08 21:11 UTC

   We've made several adjustments over the past 24 hours and are seeing improved success rates and response times across the affected APIs. However, performance remains degraded, and our engineers are continuing to work toward fully restoring service. Thank you for your continued...

5. identified 2026-10-12 08:51 UTC

   The performance stabilized for the past couple of days, so we're past the doom state. At the same time, we still see significant degradation across many of our Google engines, and we continue to work on this issue with the highest priority. We'll follow up once we have...

6. identified 2026-10-15 12:40 UTC

   We're seeing higher response times and error rates on the Google Shopping Light and Immersive Product APIs. We're actively working on these.

7. identified 2026-10-17 04:42 UTC

   Google Shopping Light and Immersive Product API issues were fixed within a few hours that same day.

8. identified 2026-10-19 22:15 UTC

   We've deployed fixes to our Google engines and have observed significant performance improvements in the Google News Light and Google Light APIs over the past few days. We're continuing to work toward a full resolution across all affected Google APIs and will provide another...

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Search API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-01 22:00 UTC

   We are currently investigating an increased error rate affecting the Yandex Search API: https://github.com/serpapi/public-roadmap/issues/4034

2. investigating 2026-10-02 02:04 UTC

   Performance has further degraded and now all requests to this API are failing. We are actively investigating this and will be sharing further updates.

3. resolved 2026-10-02 03:12 UTC

   We have implemented a fix and now the Yandex API service is operational again. We apologize for the inconvenience caused here and thank you for your patience. Feel free to reach out to contact@serpapi.com in case of any queries.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: API, Search API, Search API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-01 09:15 UTC

   We're seeing a sharp increase in error rates for our Google Search API. We're currently investigating the issue and will follow up with updates. https://github.com/serpapi/public-roadmap/issues/4376

2. monitoring 2026-10-02 01:35 UTC

   Performance has stabilized now and we continue to monitor this API.

3. investigating 2026-10-02 07:24 UTC

   We're seeing elevated error rates and response times. We're investigating.

4. investigating 2026-10-06 09:08 UTC

   The team continues their efforst on addressing the issue and finding solution as soon as possible.

5. investigating 2026-10-07 21:44 UTC

   We are continuing to investigate this issue.

6. investigating 2026-10-07 21:46 UTC

   We're continuing to work toward a solution. Since the issue now affects other APIs, the status can now be tracked here: https://status.serpapi.com/incidents/5pybr6gr3dq4 This is incident will be closed to prevent duplicate notifications. Thanks for your continued patience.

7. resolved 2026-10-07 21:48 UTC

   Closed as duplicate

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Product Reviews API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-29 17:22 UTC

   We’re currently seeing elevated response times and a decrease in success rates for the Walmart Reviews API. Our engineering team is investigating and working to restore normal performance.

2. resolved 2026-09-30 16:13 UTC

   We have released a fix for the Walmart Reviews API performance degradation and the API is fully operational.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Search API, Search API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-21 16:29 UTC

   We are currently investigating elevated response times and decreased success rates for the Google Search and Google Light API You can view the Public Roadmap issue here: https://github.com/serpapi/public-roadmap/issues/4329

2. monitoring 2026-09-22 00:32 UTC

   Google Search API response times seem to have recovered. We'll continue monitoring for stability. We're still investigating longer response times for Google Light Search API.

3. monitoring 2026-09-22 02:50 UTC

   Google Search API response times have fully recovered, and Google Light Search API performance is steadily recovering.

4. resolved 2026-09-22 02:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Jobs API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-18 19:02 UTC

   We are currently investigating long response times and low success rates for the Google Jobs API. The Public Roadmap issue can be found here: https://github.com/serpapi/public-roadmap/issues/4278

2. investigating 2026-09-19 23:16 UTC

   We're continuing to investigate this issue.

3. monitoring 2026-09-22 00:03 UTC

   Our team has deployed changes to address the performance degradation affecting the Google Jobs API, and we are seeing success rates and response times return to normal. We are continuing to monitor closely.

4. monitoring 2026-09-22 00:06 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-09-22 10:06 UTC

   We see continued performance improvement for Google Jobs API. While we still see intermittent failures, we consider the general performance degradation resolved. We've noted the current issue on our Public Roadmap: https://github.com/serpapi/public-roadmap/issues/4337

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Scholar API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-17 22:21 UTC

   We're currently seeing longer response times for Google Scholar API queries. You can find the Public Roadmap issue for this here: https://github.com/serpapi/public-roadmap/issues/4309

2. investigating 2026-09-19 23:17 UTC

   We're continuing to investigate this issue.

3. monitoring 2026-09-20 20:32 UTC

   We’ve deployed a fix and are seeing response times decrease. We’ll continue to monitor closely to ensure performance remains stable. If you continue to experience high response times with the Google Scholar API, please reach out to us at contact@serpapi.com.

4. resolved 2026-09-21 22:36 UTC

   Response times have stayed low. This incident is resolved. Please feel free to reach out if you are still facing high response times or errors with Google Scholar API.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Shopping API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-17 22:12 UTC

   We are currently investigating elevated response times and decreased success rates for the Google Shopping API. The Public Roadmap issue documenting this can be found here: https://github.com/serpapi/public-roadmap/issues/4308

2. investigating 2026-09-19 23:17 UTC

   We're continuing to investigate this issue.

3. monitoring 2026-09-22 12:45 UTC

   A fix has been implemented and we are monitoring.

4. resolved 2026-09-23 18:06 UTC

   Performance has remained stable. This is resolved.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: News API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-17 22:09 UTC

   We are currently investigating elevated response times and decreased success rates for the Google News API. You can view the Public Roadmap issue here: https://github.com/serpapi/public-roadmap/issues/4307

2. investigating 2026-09-19 23:18 UTC

   We're continuing to investigate this issue.

3. monitoring 2026-09-22 12:37 UTC

   A fix has been implemented and we are monitoring.

4. resolved 2026-09-23 18:07 UTC

   Performance has remained stable. This is resolved.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Local API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-17 22:05 UTC

   We are currently investigating long response times for Google Local API searches. A Public Roadmap issue can be found here: https://github.com/serpapi/public-roadmap/issues/4306

2. investigating 2026-09-19 23:18 UTC

   We're continuing to investigate this issue.

3. monitoring 2026-09-26 23:20 UTC

   Our team has deployed changes to address the performance degradation affecting Google Local API, and we are seeing success rates and response times return to normal. We are continuing to monitor closely.

4. resolved 2026-09-27 01:03 UTC

   The issue affecting the Google Local API has been resolved. We’re very sorry for any disruption and appreciate your patience while we worked to resolve this issue.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Local API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-11 22:52 UTC

   We are currently investigating intermittent empty responses from the Google Local API.

2. resolved 2026-09-17 22:03 UTC

   This incident was resolved, Google Local API should now be returning the expected results. Note that you may still be seeing elated response times, as documented here: https://github.com/serpapi/public-roadmap/issues/4306

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: API, Search API, Search API, Images Light API, AI Mode API, News Light API, AI Overview API, Shopping Light API, Videos Light API, Forums API, Images API, Immersive Product API, Jobs API, Lens API, Local API, News API, Scholar API, Shopping API, Short Videos API, Videos API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-10 15:59 UTC

   We currently experience service outage across all of our APIs. https://github.com/serpapi/public-roadmap/issues/4265

2. investigating 2026-09-10 16:10 UTC

   The team has deployed a temporary fix to mitigate the severity of the issue. We continue working on a long-term fix.

3. investigating 2026-09-10 18:37 UTC

   We are continuing to investigate this issue.

4. identified 2026-09-10 18:55 UTC

   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.

5. monitoring 2026-09-11 16:57 UTC

   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...

6. monitoring 2026-09-11 18:59 UTC

   We are continuing to monitor for any further issues.

7. monitoring 2026-09-11 23:29 UTC

   We are continuing to monitor for any further issues.

8. investigating 2026-09-14 10:21 UTC

   We are experiencing higher error rates and response times again. We're actively working on the issue with the highest urgency.

9. identified 2026-09-15 00:09 UTC

   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.

10. investigating 2026-09-15 08:34 UTC

    We see another performance degradation. The team is investigating and working on remediation.

11. investigating 2026-09-16 05:13 UTC

    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.

12. investigating 2026-09-16 18:21 UTC

    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...

13. monitoring 2026-09-17 10:55 UTC

    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.

14. monitoring 2026-09-17 16:38 UTC

    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...

15. monitoring 2026-09-17 18:43 UTC

    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.

16. resolved 2026-09-17 22:40 UTC

    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...

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: News API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-09-05 03:03 UTC

   We notice that Google News' success rate is decreasing. Some searches may still be successful, but the average response time is high. Related issue on GitHub: https://github.com/serpapi/public-roadmap/issues/4241

2. resolved 2026-09-07 05:02 UTC

   We've deployed a fix. We're seeing a normal performance from Google News API now.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: API, Search API, Search API, News Light API, Jobs API, Shopping API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-04 21:27 UTC

   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:...

2. identified 2026-09-05 00:17 UTC

   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.

3. monitoring 2026-09-06 17:40 UTC

   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.

4. investigating 2026-09-08 15:58 UTC

   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

5. resolved 2026-09-10 18:35 UTC

   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...

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Instagram Profile API

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-01 23:44 UTC

   Our Instagram Profile API is currently experiencing a high level of errors. We’re very sorry for the inconvenience and will share another update once we have more information or performance has fully stabilized. Related issue on the Public Roadmap:...

2. resolved 2026-09-07 06:50 UTC

   We have deployed a fix and now Instagram Profile API is operating normally.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Search API, Search API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-31 17:14 UTC

   We are currently investigating an increase in response times affecting the Google Search API and Google Light Search API, starting around 9:00 UTC this morning. Since 14:00 UTC we have been seeing signs of improvement.

2. investigating 2026-09-10 18:44 UTC

   We are continuing to investigate this issue.

3. resolved 2026-09-10 18:53 UTC

   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...

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Search API

1. identified 2026-08-26 14:33 UTC

   We've been experiencing issues with Google Search API executing very slowly or timing out entirely when advanced search operators are used in query. We've identified the issue and are currently working on a fix. https://github.com/serpapi/public-roadmap/issues/4080

2. identified 2026-08-29 19:51 UTC

   Queries with advanced search operators may also be returning an HTTP 500 error: https://github.com/serpapi/public-roadmap/issues/4213 We're continuing to work toward a fix. Thank you for your patience in the meantime.

3. identified 2026-09-19 23:31 UTC

   We're continuing to work on a fix for this issue. We'll let you know once it's implemented.

4. monitoring 2026-09-21 20:30 UTC

   We have implemented a fix to resolve this issue. We are continuing to monitor closely.

5. investigating 2026-09-22 12:56 UTC

   We're seeing higher error rates on advanced searches again. We're investigating.

6. investigating 2026-10-12 08:50 UTC

   We are continuing our work on the issue. The team has tested multiple approaches so far, but none has proved to be a long-term solution. We'll get back with additional updates as soon as possible. Thank you for your patience, and apologies for the disruption.

7. investigating 2026-10-15 15:29 UTC

   We're continuing to work on a fix for this issue. We'll reach out with additional updates as soon as possible.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Search API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-26 14:30 UTC

   Google searches with the tbm=nws parameter are currently timing out. We're investigating the issue and will follow up with updates. https://github.com/serpapi/public-roadmap/issues/4185

2. investigating 2026-09-19 23:33 UTC

   We're continuing to investigate this issue. We'll keep you updated as soon as we have any progress or new information to share.

3. identified 2026-10-12 08:49 UTC

   We're working on implementing a fix. The team noticed that the advanced inline site: operator is no longer supported in the Google Search API when using the tbm=nws flag. We recommend switching to our Google News API (https://serpapi.com/google-news-api) or dropping the site:...

4. identified 2026-10-16 21:00 UTC

   As mentioned earlier, Google doesn't serve the News tab (tbm=nws) for site: queries to signed-out users anymore. We have updated our documentation to reflect this: https://serpapi.com/search-api#api-parameters-search-query-q Those searches now result in an appropriate error...

5. resolved 2026-10-19 01:56 UTC

   Google searches using tbm=nws along with advanced parameters are now working normally. Note that Google no longer supports the site: operator for tbm=nws searches by signed-out users. Requests that use this combination will return an error message. Alternate solution is to use...

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Search API, Search API, Shopping API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-08-14 21:45 UTC

   We experienced performance degradation affecting our Google based APIs starting at 7 pm UTC. This was due to changes on Google's end. We have made some adjustments in response and are seeing recovery. We'll continue monitoring to confirm stability.

2. monitoring 2026-08-14 21:45 UTC

   We are continuing to monitor for any further issues.

3. resolved 2026-08-15 22:01 UTC

   Performance has remained stable. Thank you for your patience while we worked on this. Please reach out to us at contact@serpapi.com if you are facing any issues.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Maps Reviews API

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-14 08:40 UTC

   We are investigating higher error rates and response times on the Google Maps Reviews API. We're very sorry for the disruption. https://github.com/serpapi/public-roadmap/issues/4151

2. monitoring 2026-08-14 10:09 UTC

   We have deployed a fix that has restored normal performance. We're monitoring to ensure things remain stable.

3. monitoring 2026-08-14 11:15 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-08-14 11:16 UTC

   Performance has remained stable. This is now resolved.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: API, Search API, Ads Transparency API, Images Light API, AI Mode API, News Light API, AI Overview API, Shopping Light API, Autocomplete API, Videos Light API, Forums API, Finance API, Finance Markets API, Flights API, Flights Autocomplete API, Flights Deals API, Hotels API, Hotels Reviews API, Hotels Photos API, Images API, Immersive Product API, Jobs API, Lens API, Local API, Local Services API, Maps API, Maps Reviews API, News API, Related Questions API, Reverse Image API, Scholar API, Shopping API, Short Videos API, Travel Explore API, Trends API, Videos API, Scholar Case Law API, Maps Photos API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-07 20:57 UTC

   We’re currently experiencing an outage affecting multiple APIs. A large number of requests are failing or timing out. Our engineering team is actively investigating and treating this as our top priority. https://github.com/serpapi/public-roadmap/issues/4129

2. monitoring 2026-08-08 00:57 UTC

   Our team has released a fix, and success rates and response times have returned to expected levels for most Google APIs. A few services are still recovering, and you may experience increased response times as performance returns to normal. We continue to monitor the issue.

3. investigating 2026-08-08 10:37 UTC

   We're seeing increased response times again. We're investigating.

4. monitoring 2026-08-08 21:06 UTC

   Hi there, Our engineering team has deployed an additional fix, and performance has improved. We're continuing to monitor the situation closely before considering the issue fully resolved. We sincerely apologize for the disruption and appreciate your patience while we work to...

5. resolved 2026-08-09 13:26 UTC

   This is resolved. Thank you for your patience while we worked on this.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-06 14:52 UTC

   We are currently investigating an issue affecting the Google Events API, in which searches return empty results for all queries. Our engineering team is actively looking into the issue. We'll provide an update as soon as we have more information. Github Issue:...

2. investigating 2026-08-10 10:08 UTC

   We are continuing to investigate this issue.

3. resolved 2026-09-07 18:15 UTC

   Updating this Incident as resolved because the Google Events API has been deprecated following changes on Google's side, and we can no longer reliably provide results with the current implementation. We understand that customers still rely on this data, so we're actively...

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Place API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-04 04:36 UTC

   The Tripadvisor Place API is currently experiencing a performance degradation, with success rates dropping and elevated average response times. Customers may encounter a high rate of failed requests. We are actively investigating and will share another update once we have more...

2. resolved 2026-08-05 00:42 UTC

   A fix for the Tripadvisor Place API has been successfully deployed. Success rates and average response times have returned to normal levels. We apologize for any inconvenience this caused and appreciate your patience while we resolved the issue.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Search API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-08-01 03:25 UTC

   We're seeing a very low success rate on the Home Depot API. GitHub issue: https://github.com/serpapi/public-roadmap/issues/4106

2. identified 2026-08-10 10:03 UTC

   The team has identified the issue. We are working on a fix.

3. monitoring 2026-08-14 13:53 UTC

   We deployed a fix that should resolve the issue. We see recovery, but will continue monitoring.

4. identified 2026-08-14 20:54 UTC

   We started degrading again. The team has identified the issue. We are working on a fix.

5. identified 2026-08-17 08:46 UTC

   We're actively working on a fix. We can't share any ETA at the moment, but we will be sure to update once we have more information.

6. monitoring 2026-08-19 15:59 UTC

   A fix has been implemented, and the API has remained stable over the last day. We will continue monitoring the results to ensure the issue remains resolved.

7. monitoring 2026-08-19 22:53 UTC

   We are continuing to monitor for any further issues.

8. identified 2026-09-11 03:57 UTC

   We observed degraded performance again and the team has identified the issue. We are actively working on implementing a fix.

9. identified 2026-09-19 23:21 UTC

   We’re working on a fix, which is currently under review. We apologize for the wait and will share an update as soon as the issue is resolved. We appreciate your continued patience and understanding.

10. resolved 2026-09-21 12:29 UTC

    We've released a fix restoring the performance. Thank you for your patience.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Trends API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-29 11:06 UTC

   We are currently investigating elevated response times for our Google Trends API. https://github.com/serpapi/public-roadmap/issues/4086

2. monitoring 2026-08-01 15:55 UTC

   The performance is stable now. We'll continue monitoring.

3. resolved 2026-08-10 10:06 UTC

   The issue has been resolved and the performance is stable for the past week.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Product API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-26 15:31 UTC

   We are currently investigating elevated response times for our Home Depot Product API. https://github.com/serpapi/public-roadmap/issues/4066

2. identified 2026-08-10 10:03 UTC

   The team has identified the issue. We are working on a fix.

3. monitoring 2026-08-14 13:53 UTC

   We deployed a fix that should resolve the issue. We see recovery, but will continue monitoring.

4. identified 2026-08-17 08:46 UTC

   We're actively working on a fix. We can't share any ETA at the moment, but we will be sure to update once we have more information.

5. monitoring 2026-08-19 15:59 UTC

   A fix has been implemented, and the API has remained stable over the last day. We will continue monitoring the results to ensure the issue remains resolved.

6. monitoring 2026-08-19 22:53 UTC

   We are continuing to monitor for any further issues.

7. identified 2026-09-11 03:59 UTC

   We observed degraded performance again and the team has identified the issue. We are actively working on implementing a fix.

8. identified 2026-09-19 23:21 UTC

   We’re working on a fix, which is currently under review. We apologize for the wait and will share an update as soon as the issue is resolved. We appreciate your continued patience and understanding.

9. resolved 2026-09-21 12:28 UTC

   We've released a fix restoring the performance. Thank you for your patience.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Search API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-23 22:21 UTC

   Our eBay Search API is currently experiencing a low success rate and high response times. We’re very sorry for the inconvenience and will share another update once we have more information or performance has fully stabilized. https://github.com/serpapi/public-roadmap/issues/4063

2. identified 2026-08-01 15:44 UTC

   We've identified that the performance has been worse due to the Sold and Complete filters being hidden behind a login, making API calls with these timeout, decreasing the overall success rate.

3. resolved 2026-09-21 23:34 UTC

   We’re closing this incident as the issue is related to eBay moving the Sold and Completed filters behind a login. These filters are now only accessible to logged-in eBay users, which means we cannot scrape the data. This results in failed requests or empty results. Our...

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Search API, Search API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-07-20 21:25 UTC

   We're currently experiencing an increase in response times affecting our Google Light Search API. Our engineers are working to develope a solution.

2. monitoring 2026-07-24 05:44 UTC

   We're seeing a better response time at the moment, especially on the Google Light API

3. identified 2026-07-25 18:06 UTC

   While performance improvements have been stable for the Google Light Search API, we are still seeing longer response times for the Google Search API.

4. identified 2026-08-03 20:30 UTC

   Response times are increasing for Google Light Search API currently. Our engineers are working on a solution.

5. identified 2026-08-04 23:41 UTC

   We've made improvements to Google Light Search API and the response times have decreased on our end to an average of 0.65s.

6. resolved 2026-08-14 08:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Search API, Search API, Images Light API, AI Mode API, Shopping Light API, Forums API, Images API, Immersive Product API, Local API, Shopping API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. monitoring 2026-07-14 05:29 UTC

   We saw a decrease in success rates and slower response times on several, but not all, Google-related APIs. We've deployed a fix, and are currently monitoring the issue GitHub issue: https://github.com/serpapi/public-roadmap/issues/4025

2. investigating 2026-07-14 21:25 UTC

   We're investigating another increase in response times, most significantly affecting the Google Light Search API but also affecting other Google APIs.

3. identified 2026-07-15 22:37 UTC

   Google Light response times have returned to normal. However, some responses may still return empty results, as documented here: https://github.com/serpapi/public-roadmap/issues/4032. You may also continue to experience elevated response times across some of our Google-based...

4. identified 2026-07-15 22:52 UTC

   We are continuing to work on a fix for this issue.

5. monitoring 2026-07-17 10:06 UTC

   We implemented a fix that should restore the performance to the expected level. We'll continue monitoring the situation for the time being.

6. monitoring 2026-07-17 10:06 UTC

   We are continuing to monitor for any further issues.

7. resolved 2026-07-17 23:07 UTC

   Performance has been restored across the affected Google APIs and has remained stable over the past 24 hours. This incident has now been resolved. Thank you for your patience as we continue working to improve the resilience of our systems.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Search API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-13 21:32 UTC

   We’re investigating an issue affecting the Google Light Search API in which some paginated searches using search operators may return empty results. Our team is actively working to identify the cause and restore normal functionality. Read more here:...

2. monitoring 2026-07-13 23:36 UTC

   Our team has deployed fixes for an issue impacting multiple APIs. Success rates and response times are recovering. We are closely monitoring the platform to ensure stability. Some requests may still see elevated latency as systems fully recover.

3. resolved 2026-08-01 15:39 UTC

   The issue has been resolved for a few weeks now.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: API, Search API, Images Light API, Lens API, Local API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-07 15:46 UTC

   We're currently investigating longer response times and lower success rates across APIs.

2. identified 2026-07-07 18:16 UTC

   Our engineers identified the cause of the current performance degradation within an upstream component of our infrastructure. We are actively implementing improvements to stabilize performance across affected APIs.

3. monitoring 2026-07-08 06:13 UTC

   We're seeing a better performance for hours. However, we're still monitoring the situation.

4. resolved 2026-07-12 11:59 UTC

   The performance has been stable for the past few days after we made some changes internal changes. We'll continue monitoring and making adjustments. This issue is considered resolved now.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Search API, Search API, Ads Transparency API, Images Light API, AI Mode API, News Light API, AI Overview API, Shopping Light API, Autocomplete API, Videos Light API, Forums API, Finance API, Finance Markets API, Flights API, Flights Autocomplete API, Flights Deals API, Hotels API, Hotels Reviews API, Hotels Photos API, Images API, Immersive Product API, Jobs API, Lens API, Local API, Local Services API, Maps API, Maps Reviews API, News API, Patents API, Play Store API, Related Questions API, Reverse Image API, Scholar API, Shopping API, Short Videos API, Travel Explore API, Trends API, Videos API, Scholar Case Law API, Maps Photos API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-03 15:43 UTC

   We're seeing higher than normal response times on several, but not all, Google related APIs. https://github.com/serpapi/public-roadmap/issues/3972

2. investigating 2026-07-03 15:44 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-07-04 08:21 UTC

   We're seeing improved response time and stability for the past couple of hours. We'll continue monitoring the performance.

4. investigating 2026-07-05 18:13 UTC

   We're seeing increased response times across several Google-related APIs since the last hour. We're investigating

5. monitoring 2026-07-05 19:31 UTC

   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...

6. identified 2026-07-06 16:57 UTC

   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.

7. investigating 2026-07-06 16:58 UTC

   We are currently investigating this issue.

8. resolved 2026-07-12 12:00 UTC

   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.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-27 19:20 UTC

   We're currently experiencing longer response times and lower success rates across APIs. We're investigating the issue. Thank you for your patience in the meantime.

2. investigating 2026-06-27 19:22 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-06-27 21:13 UTC

   We've recovered from the brief outage. We'll continue monitoring the performance.

4. identified 2026-06-28 08:56 UTC

   We're seeing the issue is back. Our engineer is working on a fix.

5. monitoring 2026-06-28 21:50 UTC

   The success rate is back to normal. We'll continue monitoring the performance.

6. identified 2026-06-29 20:59 UTC

   This issue has returned. We are working to restore response times and success rates to expected levels while continuing to investigate and develop a longer-term fix.

7. identified 2026-06-30 21:16 UTC

   Success rates have returned to expected levels, but response times remain elevated. Our team is continuing to work on restoring response times to normal as soon as possible. We will provide another update as soon as possible.

8. resolved 2026-07-01 23:51 UTC

   The incident appears to be resolved, success rates and response times have returned to normal. We'll continue monitoring to ensure stabillity. Thanks for your patience, and we apologize for the impact on your business and workflows.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: AI Mode API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-24 22:40 UTC

   The Google AI Mode API is currently experiencing reduced success rates and increased response times. We’re very sorry for the inconvenience and will share another update once we have more information or performance has stabilized.

2. investigating 2026-06-24 22:41 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-06-28 22:33 UTC

   We're seeing 100% success rate since yesterday with some small hiccups. We're still monitoring the situation.

4. resolved 2026-07-04 08:55 UTC

   The performance remained stable outside of a couple of incidents, which were more general rather than Google AI Mode API-specific.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Maps Reviews API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-23 01:00 UTC

   We are currently investigating an issue affecting pagination and filtered queries for the Google Maps Reviews API, which may cause requests to fail.

2. resolved 2026-06-26 23:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Search API, Product API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-18 20:01 UTC

   We're currently investigating elevated responses times, decreased success rates, and ocassional empty results affecting the Home Depot API and Home Depot Product API.

2. monitoring 2026-07-02 00:11 UTC

   We've deployed a temporary fix about a week ago for Home Depot API and Home Depot Product API. Response times and success rates are back to normal. We are continuing to work on a more permanent solution, that we aim to roll out in the coming weeks. Thanks for your patience and...

3. resolved 2026-07-03 23:23 UTC

   The performance issues affecting Home Depot API & Home Depot Product API have been resolved. Response times and success rates have returned to normal levels. We’re very sorry for the disruption this issue caused and appreciate your patience while we worked to resolve this issue.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Travel Explore API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-06-18 05:11 UTC

   Currently, the API is returning empty results. Issue on GitHub: https://github.com/serpapi/public-roadmap/issues/3910

2. resolved 2026-07-12 12:10 UTC

   We've resolved the issue, and the results should now be returned correctly.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: API

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-08 08:16 UTC

   We're seeing an increase in our response time for Google-related APIs at the moment. We apologize for any issues it causes. Our team is currently investigating and monitoring the situation. Related issue: https://github.com/serpapi/public-roadmap/issues/3895

2. investigating 2026-06-08 18:19 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-06-08 18:20 UTC

   We have identified the root cause of elevated response times affecting our Google APIs. Our cookie generators were unable to keep up with an unexpected surge of traffic on one of our normally less-used APIs. We have prepared a solution for future surges. Response times are now...

4. resolved 2026-06-11 23:38 UTC

   Performance has remained stable over the past three days. We will continue to monitor the service and implement additional resilience improvements to help prevent similar issues in the future.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: API, Website

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-01 16:29 UTC

   We are currently experiencing an outage across our APIs and website. The team is working on restoring the services.

2. monitoring 2026-06-01 17:11 UTC

   We have implemented a fix to resolve this issue. We are continuing to monitor closely.

3. resolved 2026-06-10 18:00 UTC

   The incident has been resolved. Requests are now succeeding as expected, and the platform is operating normally again. We’re very sorry for the interruption and are grateful for your patience while we worked to restore service. We are continuing to monitor on our end.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: API, Website

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-01 11:24 UTC

   We are currently experiencing a partial outage across our APIs and website. The team is working on restoring the services.

2. resolved 2026-06-01 11:58 UTC

   We've now recovered. The team is investigating the root cause of this issue to prevent it from happening again. Our sincerest apologies for the trouble!

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: API, Website

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-05-31 07:24 UTC

   We've experienced a brief service disruption between ~6-7 AM UTC on Sunday, May 31st. This might have resulted in valid searches returning 522/525 errors. We're still investigating the issue in depth, but the observations suggest our servers may have been temporarily overloaded....

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Flights API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-21 01:34 UTC

   We are currently investigating an issue affecting the Google Flights API where searches using the `deep_search` parameter may timeout. At this time, the issue appears to impact the majority of requests made with this parameter enabled. Public Roadmap:...

2. monitoring 2026-05-21 04:06 UTC

   We have implemented a fix for the issue affecting Google Flights API searches using the `deep_search` parameter and are currently monitoring. At this time, searches appear to be processing normally again. Thank you for your patience while we worked to address this issue.

3. resolved 2026-05-22 00:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Finance API, Finance Markets API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-30 15:06 UTC

   We're seeing higher than normal response times on the Google Finance API and Google Finance Markets API. We're investigating.

2. investigating 2026-05-05 21:48 UTC

   We’re currently experiencing a major outage affecting Google Finance API and Google Finance Markets API. A large number of requests are failing or timing out. We have prioritized this issue and our engineering team is actively investigating. Related Issues on our Public Roadmap:...

3. resolved 2026-05-31 08:24 UTC

   We now support the new layout on the Google Finance website. Thank you for your patience!

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: Product API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-30 14:17 UTC

   We’re seeing elevated response times again for the Walmart Product API. Our engineering team is investigating and working to restore normal performance. Public Roadmap issue: https://github.com/serpapi/public-roadmap/issues/3739

2. monitoring 2026-05-06 15:23 UTC

   A fix has been implemented. We are monitoring the results.

3. investigating 2026-05-14 10:54 UTC

   We see another performance degradation with the Walmart Product API. We're investigating the issue.

4. resolved 2026-06-26 10:35 UTC

   This issue has been resolved and the response time for Walmart Product API is back to normal.

Excerpts are shortened. Read the full incident on SerpApi's status page.

Affected: API, Shopping Light API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-02-24 18:26 UTC

   We're currently experiencing elevated response times for most APIs, and reduced success rates on some. The Google Shopping Light API appears most affected. We're still investigating and will follow up when we have more information. Thanks for your patience in the meantime.

2. identified 2026-02-24 22:32 UTC

   The issue occurred due to changes from Google's side. We've made some temporary adjustements that should resolve the problem for the majority of APIs. Response times and success rates should be improving. Google Shopping and Google Shopping Light APIs may still be degraded or...

3. identified 2026-04-07 17:34 UTC

   We’re continuing to work on a fix to restore normal response times for the Google Shopping Light API. At this time, the issue should no longer be affecting other APIs.

4. resolved 2026-06-26 10:44 UTC

   We released an improvement that significantly reduced response times for Google Shopping Light API.

Excerpts are shortened. Read the full incident on SerpApi's status page.